[Pulp-list] webserver authentication

[Daniel Alley]

Hey Bin, sorry for the lack of response.  We did see it and we were
discussing it on Matrix - it sounds likely to be a bug.  Would you mind
filing one?  It helps with visibility since not everyone tracks the mailing
list.

https://github.com/pulp/pulpcore/issues/new/choose




On Tue, Mar 15, 2022 at 9:02 AM Bin Li (BLOOMBERG/ 120 PARK) <
bli111 at bloomberg.net> wrote:

> I tried same authentication setting on 3.18.1. It works fine with the
> postsql db installed on the same host but got a "500 internal Server Error"
> when connect to an external db. The db is not a issue because if I remove
> the settings, it works for both local and external db. I didn't find any
> useful logs. Can someone guide me how to troubleshot this issue?
>
>
> From: Bin Li (BLOOMBERG/ 120 PARK) At: 03/10/22 10:42:23 UTC-5:00
> To: pulp-list at redhat.com
> Subject: webserver authentication
>
> We are currently use the below setting for webserver authentication. It
> doesn't work anymore in 3.15. Does anyone know what should be the new
> setting?
>
> REMOTE_USER_ENVIRON_NAME: 'HTTP_REMOTE_USER'
> AUTHENTICATION_BACKENDS:
> ['pulpcore.app.authentication.PulpNoCreateRemoteUserBackend']
> REST_FRAMEWORK__DEFAULT_AUTHENTICATION_CLASSES:
> ['rest_framework.authentication.SessionAuthentication',
> 'pulpcore.app.authentication.PulpRemoteUserAuthentication']
>
> _______________________________________________
> Pulp-list mailing list
> Pulp-list at redhat.com
> https://listman.redhat.com/mailman/listinfo/pulp-list
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://listman.redhat.com/archives/pulp-list/attachments/20220316/3e158e7d/attachment.htm>