This repository has been archived by the owner on Aug 18, 2024. It is now read-only.
Change suggested ACS URL to enable more seamless SSO #7
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
With the suggested ACS URL here, things work, but there are many sign-in loops that sometimes seem to happen with certain applications - namely, Azure Data Explorer and the Azure portal. Instead, if the AAD-tenant-specific SAML URL is used (found here: https://github.com/geekzter/azure-activedirectory-gsuite-federation), these sign in loops almost never occur.
|
This is interesting but maybe not fully correct? Changing the ACS as indicated causes a SAML error "Message: AADSTS90121: Invalid empty request." Looking at this document: https://learn.microsoft.com/en-us/entra/external-id/direct-federation , their indication is the Audience URI -or EntityID is what should be updated to the specific tenant. Doing this does enable SAML to work again though their indication is without the /saml ending \o/ |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
With the suggested ACS URL here, things work, but there are many sign-in loops that sometimes seem to happen with certain applications - namely, Azure Data Explorer and the Azure portal.
Instead, if the AAD-tenant-specific SAML URL is used (found here: https://github.com/geekzter/azure-activedirectory-gsuite-federation), these sign in loops almost never occur. Since this was a change from a previous auth configuration, it required cookies to be cleared to work fully.
I discovered this today and my life has improved a lot 🙂