Issue #5779
closed
If TOKEN_SERVER includes http://, a duplicate http:// is in the realm
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.)
Updated by ipanova@redhat.com almost 5 years ago
- Project changed from Docker Support to Container Support
Updated by dkliban@redhat.com almost 5 years ago
- Triaged changed from No to Yes
- Sprint set to Sprint 62
Updated by lmjachky almost 5 years ago
- Status changed from NEW to ASSIGNED
- Assignee set to lmjachky
Updated by lmjachky almost 5 years ago
- Status changed from ASSIGNED to POST
Added by Lubos Mjachky almost 5 years ago
Added by Lubos Mjachky almost 5 years ago
Revision 8b30fe89 | View on GitHub
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.
Updated by Anonymous almost 5 years ago
- Status changed from POST to MODIFIED
Applied in changeset 8b30fe89dc51e1a1de00c18814f9ab8ef29e0826.
Updated by ipanova@redhat.com almost 5 years ago
- Status changed from MODIFIED to POST
Updated by ipanova@redhat.com almost 5 years ago
- Status changed from POST to MODIFIED
Added by Lubos Mjachky almost 5 years ago
Revision db0b33eb | View on GitHub
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
(cherry picked from commit 8b30fe89dc51e1a1de00c18814f9ab8ef29e0826)
Added by Lubos Mjachky almost 5 years ago
Revision db0b33eb | View on GitHub
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
(cherry picked from commit 8b30fe89dc51e1a1de00c18814f9ab8ef29e0826)
Updated by Anonymous almost 5 years ago
Applied in changeset db0b33eb8e6a8eabcf8d8c692f8370f00baae76e.
Updated by ipanova@redhat.com almost 5 years ago
- Status changed from MODIFIED to CLOSED - CURRENTRELEASE
.
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