Project

Profile

Help

Actions
Send by e-mail Copy link

Story #8217

closed

As a user of single container, I can easily use token auth for container registry API

Added by dkliban@redhat.com about 3 years ago. Updated almost 3 years ago.

Status:
CLOSED - DUPLICATE
Priority:
Normal
Assignee:
-
Category:
-
Sprint/Milestone:
-
Start date:
Due date:
% Done:

0%

Estimated time:
Platform Release:
Groomed:
Yes
Sprint Candidate:
No
Tags:
Single Container
Sprint:
Quarter:

Description

The instructions for the all in one container tell the user to provide a setting that disables token auth[0]. When token auth is disabled, RBAC is not used. It would be much better to provide instructions for how the user can enable token auth.

Perhaps it would be possible to enable the all in one container to check if the certs needed for token auth are present. If they are not present, the container would generate certs.

[0] https://pulpproject.org/pulp-in-one-container/

Actions
Copy link
 #1

Updated by ipanova@redhat.com about 3 years ago

  • Tags Documentation added
Actions
Copy link
 #2

Updated by mdepaulo@redhat.com almost 3 years ago

The logic in ./assets/pulpcore-api.prep already checks if the certs exist. If they do not, it does not generate them. (I'm 95% sure of this.)

So we should update the docs on how to put the certs in settings/certs/ , which maps to /etc/pulp/certs/

Actions
Copy link
 #3

Updated by mdepaulo@redhat.com almost 3 years ago

  • Groomed changed from No to Yes
Actions
Copy link
 #4

Updated by mdepaulo@redhat.com almost 3 years ago

  • Quarter set to Q2-2021
Actions
Copy link
 #5

Updated by mdepaulo@redhat.com almost 3 years ago

  • Status changed from NEW to CLOSED - DUPLICATE
Actions
Copy link
 #6

Updated by daviddavis almost 3 years ago

  • Tags Single Container added
Actions
Copy link
 #7

Updated by ipanova@redhat.com almost 3 years ago

  • Quarter deleted (Q2-2021)
  • Tags deleted (Documentation)
Actions
Send by e-mail Copy link

Also available in: Atom PDF