Refactor local SSO testing guide to use real domain example.com - #6667
Open
apata wants to merge 1 commit into
Open
Refactor local SSO testing guide to use real domain example.com#6667apata wants to merge 1 commit into
apata wants to merge 1 commit into
Conversation
zoldar
approved these changes
Sep 10, 2026
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Changes
When manually testing SSO locally, trying to register the SSO domain "plausible.test" fails with "invalid domain" error. All the SSO manual testing templates rely on the tester using that domain.
I tried to add an escape hatch to allow this domain, but it's more dev-only code that I'm not the biggest fan of.
This refactors the SSO test templates to use a real domain (example.com). It's just a bit more inconvenient.