=
["rest_framework.authentication.SessionAuthentication", "pulpcore.app.authentica
tion.PulpRemoteUserAuthentication"]
Thanks.
From: Bin Li (BLOOMBERG/ 120 PARK) At: 04/24/20 22:40:15To: dkli...@redhat.com
Cc: pulp-list@redhat.com
Subject: Re: [Pulp-list] pulpcore-client 3.2 ldap authentication
Thanks Dennis. It
Thanks Dennis. It works now by setting proxy_set_header REMOTE_USER 'admin' in
nginx.conf. It was set to $remote_user.
From: dkli...@redhat.com At: 04/23/20 08:11:20To: Bin Li (BLOOMBERG/ 120 PARK
)
Cc: pulp-list@redhat.com
Subject: Re: [Pulp-list] pulpcore-client 3.2 ldap authentication
;
> bli...@bloomberg.net> wrote:
>
>>
>> Thank Dennis. This fixes the issue restarting pulp. With my LDAP
>> credential, now I can
>> http -a id:pwd GET localhost/pulp/api/v3/status/ but getting
>> "Authentication credentials were not provided"
at.com At: 04/22/20 09:24:47To: Bin Li (BLOOMBERG/ 120 PARK
)
Cc: pulp-list@redhat.com
Subject: Re: [Pulp-list] pulpcore-client 3.2 ldap authentication
Could you please share your settings by running the following commands on your
Pulp server:
export DJANGO_SETTINGS_MODULE=pulpcore.app.sett
; entered failed state.
>> Apr 21 21:56:27 ip-1-76-158-49 systemd[1]: pulpcore-api.service failed.
>> Apr 21 21:56:27 ip-1-76-158-49 systemd[1]:
>> pulpcore-resource-manager.service holdoff time over, scheduling restart.
>>
>>
>> From: Bin Li (BLOOMBERG/ 120
entication and still need its own
authentication somehow.
From: dkli...@redhat.com At: 04/22/20 06:52:35To: Bin Li (BLOOMBERG/ 120 PARK
)
Cc: pulp-list@redhat.com
Subject: Re: [Pulp-list] pulpcore-client 3.2 ldap authentication
You need to replace
REST_FRAMEWORK['DEFAULT_AUTHENTICATI
holdoff time over, scheduling restart.
>
>
> From: Bin Li (BLOOMBERG/ 120 PARK) At: 04/21/20 21:32:49
> To: dkli...@redhat.com
> Cc: pulp-list@redhat.com
> Subject: Re: [Pulp-list] pulpcore-client 3.2 ldap authentication
>
> Yes, I did
> # pip list |grep dynaconf
> dynacon
over, scheduling restart.
From: Bin Li (BLOOMBERG/ 120 PARK) At: 04/21/20 21:32:49To: dkli...@redhat.com
Cc: pulp-list@redhat.com
Subject: Re: [Pulp-list] pulpcore-client 3.2 ldap authentication
Yes, I did
# pip list |grep dynaconf
dynaconf3.0.0rc1
From: dkli
Yes, I did
# pip list |grep dynaconf
dynaconf3.0.0rc1
From: dkli...@redhat.com At: 04/21/20 20:01:00To: Bin Li (BLOOMBERG/ 120 PARK
)
Cc: pulp-list@redhat.com
Subject: Re: [Pulp-list] pulpcore-client 3.2 ldap authentication
Did you update dynaconf to 3.0.0rc1
e. This sounds too much work for us for now.
>> configuration = pulpcore.Configuration()
>> configuration.host = 'http://localhost'
>> configuration.username = 'admin'
>> configuration.password = 'pwd'
>> rpm_client = pulp_rpm.ApiClient(configuration)
>>
>> Fro
o be added for this setup.
nginx <---http---> gunicorn <WSGI> pulpcore.app.wsgi application
Please advise
Thanks
From: dkli...@redhat.com At: 04/17/20 10:45:31To: Bin Li (BLOOMBERG/ 120 PARK
)
Cc: pulp-list@redhat.com
Subject: Re: [Pulp-list] pulpcore-client 3.2 ldap authenticat
ration.password = 'pwd'
> rpm_client = pulp_rpm.ApiClient(configuration)
>
> From: dkli...@redhat.com At: 04/16/20 08:38:38
> To: Bin Li (BLOOMBERG/ 120 PARK )
> Cc: pulp-list@redhat.com
> Subject: Re: [Pulp-list] pulpcore-client 3.2 ldap authentication
>
> Please be aware that there i
: pulp-list@redhat.com
Subject: Re: [Pulp-list] pulpcore-client 3.2 ldap authentication
Please be aware that there is a bug in dynaconf 2.2 with how settings are
merged[0]. I recommend upgrading it to dynaconf 3.0.0rc1 for best results when
configuring authentication backends in pulp.
[0] https
Please be aware that there is a bug in dynaconf 2.2 with how settings are
merged[0]. I recommend upgrading it to dynaconf 3.0.0rc1 for best results
when configuring authentication backends in pulp.
[0] https://pulp.plan.io/issues/6244
[1] https://pypi.org/project/dynaconf/3.0.0rc1/
On Wed, Apr
Pulp 3 does not currently support multiple users. We are planning to add
support for RBAC in the near future. However, I don't have a concrete
timeline for that. With all that said, you still can configure the web
server to perform authentication[0]. In this case Pulp will stop performing
I am thinking to configure nginx with ldap authentication, but I couldn't find
a way to interact with the api. Does pulpcore-client work with ldap
authentication? Has anyone made httpie work with ldap?
Thanks___
Pulp-list mailing list
16 matches
Mail list logo
