Thanks in advance.
--
You received this message because you are subscribed to the Google Groups "Google Apps Domain Information and Management APIs" group.
To view this discussion on the web visit https://groups.google.com/d/msg/google-apps-mgmt-apis/-/HxnOKCcosvoJ.
To post to this group, send email to google-app...@googlegroups.com.
To unsubscribe from this group, send email to google-apps-mgmt...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/google-apps-mgmt-apis?hl=en.
Other query's answer:1. The best way is to authenticate is using OAuth.
>Currently there is no way that you can make the Google servers poll you
>back when there is a creation/edition/deletion of a user. So only thing you
>can do is to check in timely fashion to see if any action was taken.
Are there plan to provide this functionality? or are there plans to
provide an API to retrieve the changes after a given date?
Thanks,
Jorge Luis
Hello Gunjan,
Are there plan to provide this functionality? or are there plans to
>Currently there is no way that you can make the Google servers poll you
>back when there is a creation/edition/deletion of a user. So only thing you
>can do is to check in timely fashion to see if any action was taken.
provide an API to retrieve the changes after a given date?
Thanks,
Jorge Luis
On Dec 9, 3:52 pm, Jorge Luis Mendez <jo...@iteridea.com> wrote:
> Hello Gunjan,
>
> Other query's answer:> 1. The best way is to authenticate is using OAuth.
>
> OAuth or OAuth 2.0 is the recommend method to authenticate for the
> Provisioning API?
--
You received this message because you are subscribed to the Google Groups "Google Apps Domain Information and Management APIs" group.
That really helped me clear my vision for the implementation.
On Dec 10, 2:29 am, Gunjan Sharma <gunjansha...@google.com> wrote:
> Hello Jorge
>
> OAuth 1.0 is stable and fully functional.
> where as OAuth 2.0 is easier to use but not stable yet.
> Its upto you now what you want to use.
>
> The polling by Google server issue has been a very much wanted feature. We
> already have this feature request in our issue tracker. You can star this
> issue<http://code.google.com/a/google.com/p/apps-api-issues/issues/detail?i...>and
> you will notified about what ever changes are made.
>
> Thanks
> Gunjan Sharma | Developer Programs Engineer | gunjansha...@google.com | +91
Can anyone elaborate the difference between 2-legged and 3-legged
OAuth in terms of
1. If provisioning API supports both of them?
2. A non-(Google Apps Admin) user of a domain, if grants my
application (which uses 3-legged OAuth), can create users in their
domain?
I mean, only Admin can create users and in 3-legged OAuth, the
user granting access, may not be the Admin. So in a way, how does 3-
legged OAuth handle this different to 2-legged?
Also, my app allows Google SSO with OpenID. So can the access tokens
generated and stored securely earlier, can be used in this Auth
scheme?
Thanks in advance.