Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Director/origin tests use director URL for issuer, not federation URL #2022

Open
bbockelm opened this issue Feb 14, 2025 · 1 comment
Open
Assignees
Labels
bug Something isn't working critical High priority for next release
Milestone

Comments

@bbockelm
Copy link
Collaborator

The director tests (which attempt a read/write for an origin) use the director URL for the token issuer; the intent is the federation URL.

Happily, both origin and director agree to use the director URL for the issuer so the tests should be succeeding. However, in the future we plan to have high-availability setups for the director that would cause confusion. This probably already causes confusion as everything else is starting to solidify around the federation issuer and the idea that the discovery URL is the federation issuer.

[This might also be true for the cache; I did not investigate.]

Marking this for a future release because this is strategic but has backward compatibility issues.

@bbockelm bbockelm added bug Something isn't working critical High priority for next release labels Feb 14, 2025
@bbockelm bbockelm added this to the v7.16 milestone Feb 14, 2025
@bbockelm
Copy link
Collaborator Author

Note this is different than #2020, where the director and the cache/origin currently disagree on which is the right value of the issuer URL. In this case, both sides agree on the correct URL -- I just thing they arrived at the wrong conclusion.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working critical High priority for next release
Projects
None yet
Development

No branches or pull requests

2 participants