Can the next version of 'Google Oauth Plugin' be 'Google-login-plugin' code so we don't need a new plugin and existing users can simply upgrade their plugin ?
On Saturday, November 29, 2014 10:20:15 PM UTC-6, Ryan Campbell wrote: > > Google is phasing out OpenID so the existing Jenkins plugin will become > inoperable <https://issues.jenkins-ci.org/browse/JENKINS-23431> in April. > > To address this, I wrote a google-login plugin > <https://github.com/recampbell/google-login> which uses their OAuth 2 > apis to authenticate the user. Unfortunately, you must set up a client id > and secret to use it. > > Anyway, I'd just like to make sure I can/should call the plugin > "google-login" before I do the plugin hosting dance. I think it's ok, but > trademarks. > > [image: Inline image 1] > -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/8445c8ca-e2ad-43c5-81a7-59a342a1a2bd%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
