search

straight55b / app-engine-patch

Automatically exported from code.google.com/p/app-engine-patch
0 stars 0 forks source link

Using Google Accounts user_id to identify users permanently #189

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
What steps will reproduce the problem?
1. User changes his Google Accounts email
2. User logs into app-engine-patch based website
3. A new user is created, the user can't access previous data

What is the expected output? What do you see instead?
The user should be logged in to his old account.

What version of the product are you using? On what operating system?
1.0.2.3

Please provide any additional information below.
I have attached two diffs which update the Google Accounts model to use 
user_id and fallback to email if the user_id was not in the datastore 
before.

Original issue reported on code.google.com by mbac...@gmail.com on 26 Jul 2009 at 11:12

Attachments:

GoogleCodeExporter commented 9 years ago 
Isn't this a bug in Google's SDK? I mean, their User instance isn't matching 
correctly. 
Could you please report the bug to Google?

Original comment by wkornew...@gmail.com on 26 Jul 2009 at 11:31

GoogleCodeExporter commented 9 years ago 
[deleted comment]
GoogleCodeExporter commented 9 years ago 
As you can see here, the user_id property is part of the User model and not 
generated 
by my code:

http://code.google.com/appengine/docs/python/users/userclass.html#User_user_id

Original comment by mbac...@gmail.com on 26 Jul 2009 at 11:35

GoogleCodeExporter commented 9 years ago 
Ah, ok. Thanks, I've commited it!

Original comment by wkornew...@gmail.com on 26 Jul 2009 at 11:57

GoogleCodeExporter commented 9 years ago 
Sorry, here is another small diff appending to the first one. This makes it 
automatically update the UserProperty if it has changed.

Original comment by mbac...@gmail.com on 26 Jul 2009 at 12:05

Attachments: