Actions
Issue #5779
closedIf TOKEN_SERVER includes http://, a duplicate http:// is in the realm
Start date:
Due date:
Estimated time:
Severity:
2. Medium
Platform Release:
OS:
Triaged:
Yes
Groomed:
No
Sprint Candidate:
No
Tags:
Documentation
Sprint:
Sprint 63
Quarter:
Description
If the setting TOKEN_SERVER is listed like: http://localhost:24816
rather than: localhost:24816
Then when you go to run:
$ http 'http://localhost:24816/v2/'
The output includes:
realm="http://http://localhost:24816/token
This may be a docs issue, or a code issue. Either way, it complicates users following the instructions:
https://pulp-container.readthedocs.io/en/latest/workflows/authentication.html
Which states "A fully qualified domain name of a token server" (And an FQDN would not include the port.)
Actions
Do not prepend a scheme to a token server in the Www-Authenticate header
In this commit, there was also updated the documentation. Before this commit, there was not mentioned that pulp_container expects a FQDN of a token server together with a port number. The additional setting CONTENT_HOST was created because the token server should expect only service names wihthout a scheme.
closes #5779 https://pulp.plan.io/issues/5779