This link has been bookmarked by 22 people . It was first bookmarked on 30 Oct 2008, by someone privately.
-
Don Doge and OAuth) use namespace aliases, such as "ax", for convenience only. OpenID libraries specify their own namespaces. Google authentication will recognize the parameters if the values are set correctly, regardless of name.
-
-
This extension allows web developers to open Google authentication in a popup window for a smoother experience.
-
If the user approves the authentication, Google returns the user to the URL specified in the openid.return_to parameter of the original request. A Google-supplied identifier, which has no relationship to the user's actual Google account name or password, is appended as the query parameter openid.claimed_id. If the request also included attribute exchange, additional user information may be appended. For OpenID+OAuth, an authorized OAuth request token is also returned
- 2 more annotations...
-
-
Carsten PötterDescribes federated login for Google account users.
-
Cezary PlumDokumentacja opisująca wykorzystywanie kont Googla przez inne strony internetowe (via OpenID).
-
-
Add attribute exchange to the authentication requests.
(Optional)
Include the attribute exchange parameters to authentication requests to get the user's email address as well as their login ID.
When including the attribute exchange parameters in an authentication request, keep in mind that the parameter names do not need to match those defined by Google. OpenID libraries construct requests using their own names. Google uses the namespace alias ext1 for these parameters but you can specify any alias you choose (openid.ns.<alias>). The critical issue is that the values of these parameters be set to the strings specified in the API reference.
-
Would you like to comment?
Join Diigo for a free account, or sign in if you are already a member.