|
It issue has already been seen on OSQA meta, i.e. in Stack Exchange migration to same domain break Google OpenIDs. I suppose I do have a very same problem with my migrated site. I started testing from Google OpenID logins and it appears that when I login with Google OpenID for existing user, the OSQA instance thinks that I'm totally new user. I did some debugging and assoc_key that I'm getting whlie trying to login with OSQA is different that the one in (migrated) db - so clearly OSQA thinks that it's a new user. I'll add that we stayed with a domain from before migration - so different domain is not the issue. Furthermore I investigated what requests are sent to Google while trying to authenticate. Hence, OSQA sends:
And SE sends:
It's easy to see that these two are different. OSQA uses AX and SE uses SREG. return_to link is different. How to get Google OpenID working? |
|
I think that the key that identifies the user in the case of Google Open Id depends on the return URL. You can try using the same return URL that was using StackExchange. Just passing it to Google and redirecting it to the URL which OSQA needs could be enough. |
@rafek, "Google OpenID auth does not work for migrated users (from SE)" is not a questions. All postings at meta are required to have clear, specific questions as their title. Please edit immediately or this posting may be deleted. Thank you.