google-login plugin

281 views
Skip to first unread message

Ryan Campbell

unread,
Nov 29, 2014, 11:20:15 PM11/29/14
to jenkin...@googlegroups.com
Google is phasing out OpenID so the existing Jenkins plugin will become inoperable in April.

To address this, I wrote a google-login plugin 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.

Inline image 1

Christopher Orr

unread,
Nov 30, 2014, 5:07:07 PM11/30/14
to jenkin...@googlegroups.com
There are already quite a few plugins with "Google" in the name.

In fact, the Google OAuth Plugin (developed by Google) would appear to
have some overlap with this one:
https://wiki.jenkins-ci.org/display/JENKINS/Google+OAuth+Plugin

Is there maybe some scope for integration between the two?

Regards,
Chris


On 11/30/2014 05:20 AM, 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.
>
> 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 jenkinsci-de...@googlegroups.com
> <mailto:jenkinsci-de...@googlegroups.com>.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-dev/CANHK%3DJ0q2O63akmjjtXoG1Gto-HkwPBL6GLdJdoesZtx7OjM8w%40mail.gmail.com
> <https://groups.google.com/d/msgid/jenkinsci-dev/CANHK%3DJ0q2O63akmjjtXoG1Gto-HkwPBL6GLdJdoesZtx7OjM8w%40mail.gmail.com?utm_medium=email&utm_source=footer>.
> For more options, visit https://groups.google.com/d/optout.

Ryan Campbell

unread,
Nov 30, 2014, 5:36:18 PM11/30/14
to jenkin...@googlegroups.com
There's certainly scope for integration from what I can tell. The google-login plugin could request additional scopes needed by various plugins, which would result in tokens being available for use to the various google plugins.

I don't see the overlap per se, but perhaps I'm missing something. They are both obtaining oauth tokens, but via different means.

But perhaps google-login could be subsumed into google-oauth. They have similar dependencies and I would imagine there would be a healthy intersection of their user bases.

On Sun Nov 30 2014 at 4:07:07 PM Christopher Orr <ch...@orr.me.uk> wrote:
There are already quite a few plugins with "Google" in the name.

In fact, the Google OAuth Plugin (developed by Google) would appear to
have some overlap with this one:
https://wiki.jenkins-ci.org/display/JENKINS/Google+OAuth+Plugin

Is there maybe some scope for integration between the two?

Regards,
Chris


On 11/30/2014 05:20 AM, 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.
>
> 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
--
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 jenkinsci-dev+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/547B9502.5060409%40orr.me.uk.

Kenny Garland

unread,
Dec 1, 2014, 2:10:51 PM12/1/14
to jenkin...@googlegroups.com
Very excited about this plugin, thank you Ryan!

Surya Gaddipati

unread,
Dec 1, 2014, 5:33:49 PM12/1/14
to jenkin...@googlegroups.com
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 ?

Ryan Campbell

unread,
Dec 2, 2014, 10:37:52 AM12/2/14
to jenkin...@googlegroups.com
I went ahead and released it as google-login 1.0

--
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 jenkinsci-de...@googlegroups.com.
 To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/8445c8ca-e2ad-43c5-81a7-59a342a1a2bd%40googlegroups.com.
Reply all
Reply to author
Forward
0 new messages