You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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.
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.
The text was updated successfully, but these errors were encountered: