How does Google generate OpenID identifier tokens?

I use the module django_openid_authand set it to automatically create new accounts for new OpenIDs. This makes the “sign-up” process really trivial, but I'm a little worried that due to Google generating its OpenID tokens, it might accidentally create a new account for an existing user, giving them the impression that the data in their original account was lost .

As far as I can tell, Google will generate different declared IDs for different domain names. This www.site.com and site.com will create two different tokens and, therefore, two accounts on my system. I fixed this by redirecting www.site.com to the .com website.

Are there any other errors I should be aware of? And can someone point me in the direction of some details about what Google uses to generate the identifier?

+3
source share
2 answers

From the docs :

openid.realm

Authenticated area. Specifies the domain to which the end user is being requested. (Example: "http: //*.myexamplesite.com"). This value must match the domain defined in openid.return_to. If this parameter is not defined, Google will use the URL specified in openid.return_to.

Google Federated Login, . , Google.

+4

Source: https://habr.com/ru/post/1725135/


All Articles