From: Christopher J. Morrone <morrone2@llnl.gov>
To: lustre-devel@lists.lustre.org
Subject: [lustre-devel] OpenID 2.0 and Gerrit 2.11
Date: Wed, 03 Jun 2015 14:24:08 -0700 [thread overview]
Message-ID: <556F7078.1020407@llnl.gov> (raw)
In-Reply-To: <1637F3AC-75FF-4EEC-8777-4FBF9FCDB60B@intel.com>
Is it perhaps that gerrit doesn't entirely support it natively, but
there is an external gerrit plugin (gerrit-oauth-provier) that makes it
work with gerrit 2.10.3.1 or 2.11? Their documentation is none too clear.
Chris
On 06/03/2015 01:14 PM, Read, Robert wrote:
> Right, we need OAuth2, which is what Google calls Google OpenID Connect. It looks this has been addressed as of Gerrit 2.10.2.
>
> https://code.google.com/p/gerrit/issues/detail?id=2677
>
>
> robert
>
>
> On Jun 3, 2015, at 13:03 , Colin Faber <colin.faber at seagate.com<mailto:colin.faber@seagate.com>> wrote:
>
> Hi Chris,
>
>>From what I can tell, the OAuth2 and OpenID 2.0 combo does work for google account authentication against gerrit:
>
> http://gerrit.cloudlinux.com:8080/login/%23%2Fq%2Fstatus%3Aopen
>
>
> -cf
>
>
>
> On Wed, Jun 3, 2015 at 1:55 PM, Christopher J. Morrone <morrone2 at llnl.gov<mailto:morrone2@llnl.gov>> wrote:
> I think you might have that backwards. Google has _stopped_ supporting OpenID 2.0. To the best of my knowledge no version of gerrit yet supports Google's new OpenID Connect system.
>
> Chris
>
>
> On 06/03/2015 12:52 PM, Colin Faber wrote:
> Hi,
>
> This is probably more a question for the folks at Intel.. Is there an
> ETA or plan in place to upgrade to Gerrit 2.11 and OpenID 2.0? Such
> changes would allow for google logins to function correctly.
>
> -cf
>
>
>
> _______________________________________________
> lustre-devel mailing list
> lustre-devel at lists.lustre.org<mailto:lustre-devel@lists.lustre.org>
> http://lists.lustre.org/listinfo.cgi/lustre-devel-lustre.org
>
>
> _______________________________________________
> lustre-devel mailing list
> lustre-devel at lists.lustre.org<mailto:lustre-devel@lists.lustre.org>
> http://lists.lustre.org/listinfo.cgi/lustre-devel-lustre.org
>
> _______________________________________________
> lustre-devel mailing list
> lustre-devel at lists.lustre.org<mailto:lustre-devel@lists.lustre.org>
> http://lists.lustre.org/listinfo.cgi/lustre-devel-lustre.org
>
>
next prev parent reply other threads:[~2015-06-03 21:24 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-03 19:52 [lustre-devel] OpenID 2.0 and Gerrit 2.11 Colin Faber
2015-06-03 19:55 ` Christopher J. Morrone
2015-06-03 20:03 ` Colin Faber
2015-06-03 20:14 ` Read, Robert
2015-06-03 20:32 ` Colin Faber
2015-06-03 21:02 ` Simmons, James A.
2015-06-03 21:24 ` Christopher J. Morrone [this message]
2015-06-03 21:25 ` Colin Faber
2015-06-03 23:44 ` Jones, Peter A
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=556F7078.1020407@llnl.gov \
--to=morrone2@llnl.gov \
--cc=lustre-devel@lists.lustre.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.