google-openid

问题 I am using the Google Data Protocol Client Libraries for authenticating my users. Here is the code I have so far: GoogleOAuthParameters oauthParameters = new GoogleOAuthParameters(); oauthParameters.setOAuthConsumerKey(CONSUMER_KEY); oauthParameters.setOAuthConsumerSecret(SECRET_KEy); GoogleOAuthHelper oauthHelper = new GoogleOAuthHelper(new OAuthHmacSha1Signer()); oauthParameters.setScope(SCOPE); oauthParameters.setOAuthVerifier(oauth_verifier); oauthParameters.setOAuthToken(oauth_token);

问题 I'm writing a python script that scrapes a website, where the website uses OpenID auth to identify me via google. Is there a python library that will handle do this for me, or do I need to find out and replicate the steps that my browser already does? Otherwise, is there some standard way of doing this in some other language? 回答1: From the client's perspective, an OpenID login is very similar to any other web-based login. There isn't a defined protocol for the client; it is an ordinary web

问题 Since Google deprecated OpenID 2.0 https://developers.google.com/accounts/docs/OpenID2 What django libraries are present which support the new settings? I am trying to add Google OpenID using django_openid_auth (that's on launchpad) and getting a 400 error as response!! What are the additional changes I should make so that django_openid_auth works with new Google config 回答1: I would say Python-social-auth works well. I use it in almost every project and never gave any problem. 来源： https:/

问题 Google updated their OpenID Connect endpoints to be fully spec compliant, as part of the OpenID Certification effort. I rely on OpenID Connect to sign my users in with Google. Will I need to do anything as a relying party to avoid breaking due to these changes? 回答1: It depends on how you use OpenID Connect with Google. If you are performing dynamic discovery by fetching https://accounts.google.com/.well-known/openid-configuration as recommended by the docs then the way your servers interact

问题 I am currently using the Users API (this one here) with the Go language on my Google App Engine application. My users are getting the warning message when they first grant permissions that says "OpenID 2.0 for Google accounts is going away. Developers should migrate to OpenID Connect by April 20, 2015." But I can't find any warnings in the documentation for the Users API anywhere saying that anything will stop working, like I do all throughout other sections regarding OpenID 2.0 (here). I am

问题 As we know Google Login is migrating from OpenId2.0 to OpenId connect. I have changed my code as like require 'oauth/openid.php'; $openid = new LightOpenID; $openid->realm = "http://".$_SERVER[HTTP_HOST]; $openid->identity = 'https://www.google.com/accounts/o8/id'; $openid->required = array('contact/email'); if (!headers_sent()){ header('Location: '.$openid->authUrl()); }else{ echo '<script type="text/javascript">'; echo 'window.location.href="'.$openid->authUrl().'";'; echo '</script>'; } }

问题 I want users to my website to use Google Accounts to authenticate / sign in to my website. The primary use case being users will edit and generate content and we want to log ownership in a secure way. We are not interested in obtaining users Google data, we just want a means to authenticate users. After googling, I came across some documentation, which seems to explain how to do this OpenID Connect (OAuth 2.0 for Login). But the documentation immediately says "Note: If you want to provide a

问题 Say I have the following response from Google's OAuth2 /token endpoint after exchanging the code obtained from the /auth endpoint (using this example OAuth Playground request): { "access_token": "ya29.eQETFbFOkAs8nWHcmYXKwEi0Zz46NfsrUU_KuQLOLTwWS40y6Fb99aVzEXC0U14m61lcPMIr1hEIBA", "token_type": "Bearer", "expires_in": 3600, "refresh_token": "1/ZagesePFconRc9yQbPxw2m1CnXZ5MNnni91GHxuHm-A", "id_token": "eyJhbGciOiJSUzI1NiIsImtpZCI6IjJhODc0MjBlY2YxNGU5MzRmOWY5MDRhMDE0NzY4MTMyMDNiMzk5NGIifQ

问题 My company uses Google Apps for our e-mail/business app provider. Every employee has an account here. I'm looking into creating an asp.net web app that would allow users to sign-in (using their Google Apps account) and then accomplish certain things (first goal: keep a current record of the employee's skillset). Before I get started, I wanted to find out if an OpenID login system using Google Apps is any more difficult than doing it the standard way, or if I need to be aware of any pitfalls.

问题 In Google's OpenID Migration Guide, for transitioning from OpenID 2.0 to OpenID Connect, step 1 is that I need to obtain OAuth credentials for my application. One thing I like about "regular" OpenID is that I can allow my users to authenticate from any IDP of their choosing. Whether they use Google, Yahoo, or any other endpoint, as a developer I don't need to go through the trouble of manually obtaining OAuth credentials from each of those providers and configuring my application to support