Docs: Update SSO with Auth0 guide DRAFT #26488
Draft
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.
Description
The Jira tickets asks to clarify the use of callback URL
localhost:4649
in the guide. When I tested the guide, I noticed that the Auth0 steps are outdated.post-login
trigger. Auth0 doesn't have docs on how to do that. (I also found Auth0 and Nomad docs content that no longer matches the Auth0 dashboard UI).Note
The process in the original tutorial works, but I couldn't find any Auth0 documentation to support the custom action content, so I updated using the process Auth0 has documented.
This page was moved verbatim from tutorials in Nomad IA phase 1 so backport only to stable-website and 1.10.x.
Testing & Reproduction steps
Links
Jira: CE-1001
Deploy preview https://nomad-git-ce1001oidc-hashicorp.vercel.app/nomad/docs/secure/authentication/sso-auth0
Contributor Checklist
changelog entry using the
make cl
command.ensure regressions will be caught.
and job configuration, please update the Nomad website documentation to reflect this. Refer to
the website README for docs guidelines. Please also consider whether the
change requires notes within the upgrade guide.
Reviewer Checklist
backporting document.
in the majority of situations. The main exceptions are long-lived feature branches or merges where
history should be preserved.
within the public repository.