-
Notifications
You must be signed in to change notification settings - Fork 40
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Develop documentation for Okta #15995
Develop documentation for Okta #15995
Conversation
Dependency Review✅ No vulnerabilities or license issues or OpenSSF Scorecard issues found.OpenSSF Scorecard
Scanned Manifest Files |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I added some comments that I think would make sense to add for somebody that has to maybe set this up from scratch?
Our use of okta in frontend is configured by the following environment variables whose values can be found in the application listing within Okta: | ||
-VITE_OKTA_CLIENTID | ||
-VITE_OKTA_URL | ||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Could we add more documentation around how we get the client id and OKTA URLs for each environment?
If that's documented somewhere else can we reference that here?
Maybe also some details on where these environment variables are used and how the Okta widget is set-up?
Quality Gate passedIssues Measures |
Fixes #13868
This PR adds updated and new documentation regarding our use of Okta.