Hi Jeffrey, Thanks for the question. The Email Migration API works with OAuth and OAuth2, as described in this article<https://developers.google.com/google-apps/email-migration/auth> .
To get a feeling for how this works, you can try authenticating in the OAuth2 Playground <https://code.google.com/oauthplayground> with the scope https://apps-apis.google.com/a/feeds/migration/. Cheers, Stafford On Thursday, May 17, 2012 2:59:30 PM UTC-7, Jeffrey McKay wrote: > > I have an application that uses the email migration API, and it > authenticates via ClientLogin, as I believe is the only support way of > doing it. Am I wrong about that? The reason I ask is that ClientLogin is > now "depreciated" and supposedly will go away April 20, 2015. Will the > email migration API support OAuth 2.0? If so, how exactly is the ability > to perform a migration on behalf of a user done (without knowing the user > password)? > > -- 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/-/e7syvXAo7LQJ. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/google-apps-mgmt-apis?hl=en.
