Hi Michael, I'm looking to add Admin Audit API support to my open source project, Google Apps Manager (GAM) <http://code.google.com/googleapps/support/>. Since most of the Provisioning APIs are still OAuth 1.0 I haven't added OAuth 2.0 to GAM. I'm trying to understand a few things with the new requirements:
- Is it safe to assume that ClientLogin will not work with Admin Audit API? There is no mention of ClientLogin at all in the docs. I know it's being deprecated. If it's not supported though it might be worth explicitly saying so in the Admin Audit API docs. - With GAM being open source and an installed app (not web based), how should this work? Is there any issue with publishing a dev console key in the GAM source or is that a security risk? If so will each user running GAM need to generate their own dev console key? - The docs clearly state that you cannot use the non-registered 'anonymous' values for consumer key/secret which is exactly what GAM does right now. How should GAM handle this? Again is it safe to publish the consumer key/secret for GAM in source or will each user need to generate their own consumer key/secret for GAM in addition to the regular 3-legged OAuth process? My goal is to get the Admin Audit API working with GAM while requiring as little additional work for end users as possible. Thanks for any help you can provide. Jay -- 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/-/SVfPNLydBzkJ. 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.
