We are developing a suite of intranet applications from the ground up and we also are Google Apps for Enterprise customers. (So far as Google are concerned our Intranet is like any other web application so the mechanics of that are irrelevant)
We have registered the intranet url (publicly accessible) with Google, yet on during the 3 legged authorisation/login sequence, only the url is shown as requesting permission to access data and not the registered application description. When manually adding the url to the global authorised set of accessing applications, the displayname propagates into the set of approved applications alongside installed marketplace apps. We expected two things from that addition process. One, that the act of globally adding it with applicable scopes would remove the need for our users to grant access at all. Or at least secondly, that the act of registering the application URL with google would allow the correct displayname to be that requesting access permission. The process technically works fine and the approval is working, it is just missing the displayname nicety. Given that the registered name is visible within Google Apps panel is the likely cause a slightly malformed token request? Thanks Jonathon -- You received this message because you are subscribed to the Google Groups "OAuth" 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://groups.google.com/group/oauth?hl=en.
