Open qdrop17 opened 3 months ago
@qdrop17 unfortunately, the mapping here is one to one, and can't accept a list of values. The one thing docs team can do here is clear up the wording to make that more evident.
@qdrop17 unfortunately, the mapping here is one to one, and can't accept a list of values. The one thing docs team can do here is clear up the wording to make that more evident.
Okay, got it. Do you mind mentioning someone from the development team to clarify this feature? To us, it's unclear if Rancher supports multiple redirect URIs or not. We would greatly appreciate this capability.
@JonCrowther or @samjustus could you address?
To us, it's unclear if Rancher supports multiple redirect URIs or not. We would greatly appreciate this capability.
That's correct. You can modify the 1 listed domain manually, but never have more than one at the same time. As far as supporting multiple, it is on our radar, but hasn't been prioritized yet. If you'd like to leave a comment on https://github.com/rancher/rancher/issues/23671, that would help bring attention to the feature.
Summary
The process of configuring multiple redirect URIs for Azure AD-enabled authentication is not well documented. The relevant documentation can be found at:
While the file provided contains the necessary information, it is presented as a key-value pair rather than a list. As a result, we are unsure how to configure an additional redirect URI for our external exposure.
It would be great to clarify how this can be done properly.
Related Issues
https://github.com/rancher/rancher/issues/23671