|
I just switch our site to OSQA with the same hostname and urls. Everything works greats including old links. However, Google OpenIDs are broken. Any workarounds. suggestions? Other OpenIDs, such as yahoo, appear to work great. |
|
Actually I found the bug in the code and have a fix. The issue is that SE sends the following realm: "http://meta.stackoverflow.com/users/authenticate/" to Google. While OSQA was sending "http://meta.stackoverflow.com/" So I updated the code to use http://meta.stackoverflow.com/users/authenticate/ and everything worked perfectly with Google. The change required 2 updates:
change '/' to '/users/authenticate/' for 'OPENID_TRUST_ROOT' Wow, great catch! It's weird, however, that ANY other site EVER worked, and most of them always did. I wonder if this is something that varies from one StackExchange site to another?
(18 Jul '10, 01:33)
rickross ♦♦
Did this fix get confirmed as working? I note that the source I have does not have this change made and we're more than 6 months later on in time.
(01 Apr '11, 09:56)
dendrophile
Wait, @Randell, isn't this fix included in the main codebase?
(03 Apr '11, 00:49)
ripper234 ♦
Not on the first few versions, I think. We had logging-in problems using Google OpenID.
(03 Apr '11, 01:32)
Randell
In our install, I found that older Google OpenID registrants migrated from StackExchange began working once we applied the change above. Google OpenID registrants using a Google profile, however, still did not work, ie, those that used either www.google.com/profiles/profilename or profiles.google.com/profilename as their OpenID URL. Fortunately in our case, very few users had Google profiles, and we manually corrected the issue.
(14 Apr '11, 16:11)
farmerguy
Will applying this fix that enables the old Google profiles log in mess up with the current users who are able to login using Google? I'm afraid that applying this fix will allow those users who can't login, login, while making those who can already log in, not log in. Also, has this fix been added to the trunk already?
(20 Apr '11, 08:25)
Randell
showing 5 of 7
show 2 more comments
|
|
Google OpenIDs are the most particular of any we have seen, so you must have an absolutely exact match on the seed URL that is used to generate the hash. So far, this has always worked. It is possible some other issue is blocking these logins. |
