Date: prev next · Thread: first prev next last
2015 Archives by date, by thread · List index


Google OpenId is going to turn off by April 20...

Google's OpenID help page[1] says OpenID 2.0 is superseded by OpenID
Connect. The page says: "Please complete your migration to OpenID Connect
or Google+ Sign-in before the shutdown date." So the service isn't going
away, just the particular protocol is, to be replaced with a different and
presumably better, protocol.

So, unless Gerrit has decided not to, or is unable to, migrate to OpenID
Connect by the deadline, migrating to OpenID Connect should be seamless and
uneventful.

Do we know whether or not Gerrit will have migrated by the deadline?
(Granted, warning people to avoid a lockout is wise.)

[1] https://developers.google.com/accounts/docs/OpenID

On Sat, Feb 21, 2015 at 4:42 PM, V Stuart Foote <VStuart.Foote@utsa.edu>
wrote:

V Stuart Foote wrote
Hmm, so looks like there is an issue with gerrit project's implementation
of openid4java and StackExchanges OpenID (also using openid4java).

s/(also using openid4java)/(using DotNetOpenAuth)/



--
View this message in context:
http://nabble.documentfoundation.org/IMPORTANT-Google-OpenId-End-of-Life-Gerrit-users-need-to-take-action-tp4140900p4140925.html
Sent from the Dev mailing list archive at Nabble.com.
_______________________________________________
LibreOffice mailing list
LibreOffice@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/libreoffice


Context


Privacy Policy | Impressum (Legal Info) | Copyright information: Unless otherwise specified, all text and images on this website are licensed under the Creative Commons Attribution-Share Alike 3.0 License. This does not include the source code of LibreOffice, which is licensed under the Mozilla Public License (MPLv2). "LibreOffice" and "The Document Foundation" are registered trademarks of their corresponding registered owners or are in actual use as trademarks in one or more countries. Their respective logos and icons are also subject to international copyright laws. Use thereof is explained in our trademark policy.