Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:117834
MIME-Version: 1.0
References: <DU0PR02MB80956C2E31F00EFA472D706C8CDB9@DU0PR02MB8095.eurprd02.prod.outlook.com>
 <cc8b5e24-8d1e-82d2-9abd-9527364007e3@heigl.org> <6293d2f2.1c69fb81.78e38.c94cSMTPIN_ADDED_MISSING@mx.google.com>
In-Reply-To: <6293d2f2.1c69fb81.78e38.c94cSMTPIN_ADDED_MISSING@mx.google.com>
Date: Mon, 30 May 2022 13:51:31 +0200
Message-ID: <CAPzBOBMzg28J+t+OYFwWky2677cB1B7rrNgEB-yCFJR6h8JQUQ@mail.gmail.com>
To: Ben Ramsey <ramsey@php.net>
Cc: internals <internals@lists.php.net>
Content-Type: text/plain; charset="UTF-8"
Subject: Re: [PHP-DEV] [RFC][Under discussion] Create a global login system
 for php.net
From: landers.robert@gmail.com (Robert Landers)

On Sun, May 29, 2022 at 10:09 PM Ben Ramsey <ramsey@php.net> wrote:
>
> On 5/29/22 09:57, Andreas Heigl wrote:
> > But the bad news is, that there is also the colobus system which powers
> > the NNTP-server backend that a number of people use to interact with the
> > mailing-list. Which also has an authentication and would therefore need
> > to be switched. So we are back at 9 services. And we switched one that
> > is completely under our control to one that isn't as we are merely using
> > a (rather old by now) service.
>
> I've looked into colobus a fair amount, and it does not use
> authentication itself. It accepts requests to post to newgroups, but
> then it appears to primarily act as a proxy for ezmlm, which has it's
> own form of authentication, and we're not going to be able to tie the
> ezmlm authentication to GitHub.
>
> --
> Cheers,
> Ben

There's also the OAuth Proxy project:
https://oauth2-proxy.github.io/oauth2-proxy/docs/features/endpoints
which allows you to use some baked-in features of nginx in order to
provide unauthenticated/legacy services with protection and
appropriate authentication headers:
https://nginx.org/en/docs/http/ngx_http_auth_request_module.html.