-
Notifications
You must be signed in to change notification settings - Fork 319
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Google+ deprecation #1526
Comments
* Setting goo auth to read only for a while until this is clarified at passport strategy NOTE: * Untested on pro but seems to work on dev Applies to OpenUserJS#1526
* Setting goo auth to read only for a while until this is clarified at passport strategy NOTE: * Untested on pro but seems to work on dev Applies to #1526 Auto-merge
Successful login to OUJS with no changes to source. Perhaps they haven't done it yet?... or perhaps that alias someone was talking about? I will check again periodically throughout the day. |
Okay... definitely past the deadline... still able to log in (and observed at least two others with goo logging in successfully). I did remove g+ from my other account before all of this. Guess either the Sometime next week I'll retry allowing new account creations. |
* Please read their CHANGELOGs * Google auth dep update ... new default userInfo endpoint... applies to OpenUserJS#1526 . Tested with dev existing... same token returned as before. * Delete op retested
* Please read their CHANGELOGs * Google auth dep update ... new default userInfo endpoint... applies to #1526 . Tested with dev existing... same token returned as before. * Delete op retested Auto-merge
Interesting read at https://www.bbc.com/news/technology-47771927 ... Tuesday is their EOL? |
Here we go again???
Refs:
In the short term we should probably disable new Google auths @sizzlemctwizzle
Historical refs:
profile
vs. what was done here. e.g. no path.Ref:
Over at PR No. 51 on the package issue tracker it states:
... seems to also fix OpenID which I was told and read by Goo that it was deprecated. We took action upon that in #484 ... a trite bit confusing to see that fix under a file named openid
The text was updated successfully, but these errors were encountered: