Thanks for your reply. Once your application has gained user-trust the trust stays until the user > choses to revoke it. >
I suspected this, but good to know for sure. > > The URL that you specify when you get your appkey from Google is a > callback. Google redirect the user session back to you with an > authorisation code as a parameter. Your app grabs the authcode and you're > in. > As I understand this, the callback can only be made if you specify a return-address (so to speak). But since my app can be run from anywhere there is no return-uri so the user is presented with a page with a readable authorisation-code. this is what happens: 1. User starts app for the first time in browser 2. User is taken to consent-page of Google (either in same window or new browser window/tab) At this point, there is no actual communication anymore between my app and whatever the user does. 3. The user authorises the app and gets taken to a page that displays the authorisationcode with the text that user must copy/paste this. I would like to circumvent this if possible? the reason is that I suspect not all my users to be so tech-savy to understand how to copy/paste this. -- You received this message because you are subscribed to the Google Groups "Google Contacts, Shared Contacts and User Profiles APIs" group. 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://code.google.com/apis/contacts/community/forum.html
