Project

General

Profile

Actions

Bug #34668

closed

Katello - Feature #34669: Upgrade to pulpcore 3.18

upgrading to pulpcore 3.18 *may* require a change to AUTHENTICATION_BACKENDS

Added by Justin Sherrill almost 3 years ago. Updated over 2 years ago.

Status:
Rejected
Priority:
Normal
Assignee:
-
Category:
Foreman modules
Target version:
-
Difficulty:
Triaged:
No
Fixed in Releases:
Found in Releases:

Description

Its unclear yet, but opening for documentation, we may need to update our pulp installation to use:

AUTHENTICATION_BACKENDS = [
'django.contrib.auth.backends.RemoteUserBackend',
]

related to https://github.com/pulp/pulpcore/issues/2260

after some discussion we think its unlikley this will actually need to be done, but i wanted to open an issue to capture it in case it does.

Actions #1

Updated by Justin Sherrill almost 3 years ago

  • Parent task set to #34669
Actions #2

Updated by Brian Bouterse almost 3 years ago

I revised the Pulp docs here based on some of my testing: https://github.com/pulp/pulpcore/pull/2399/files

To recap the convo where we determined we don't think katello needs a change:
1. katello creates the 'admin' user in its installer (this is a django user in pulp's DB created with pulpcore-manager ...)
2. The external auth configured today is expected to receive the 'admin' user from the DB
3. Because the user exists in the DB, and that user is an admin, the default permission_classes of Pulp should continue to allow everything to work since admins pass all permissions checks.

Actions #3

Updated by Ian Ballou over 2 years ago

  • Status changed from New to Rejected

Closing since it's not needed.

Actions

Also available in: Atom PDF