-
Notifications
You must be signed in to change notification settings - Fork 47
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
docs(token-vault): add readme #375
Conversation
|
packages/token-vault/README.md
Outdated
1. **Client ID**: Any alphanumeric string can be used here to identity this client | ||
2. **Client secret**: keep this blank | ||
3. **Sign-in URLs**: This URLs should be fully qualified URLs that you want ForgeRock to redirect to provide the Authorization Code for you to collect tokens; if you're using a dynamic value like `location.href`, make sure to pay close attention to trailing slashes | ||
4. \*\*Grant typ |
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 think we have a cutoff here?
☁️ Nx Cloud ReportCI is running/has finished running commands for commit a1a8d11. As they complete they will appear below. Click to see the status, the terminal output, and the build insights. 📂 See all runs for this branch ✅ Successfully ran 5 targetsSent with 💌 from NxCloud. |
Your preview environment pr-375-ryanbas21 has been deployed. Preview environment endpoints are available at: |
8505d4a
to
a1a8d11
Compare
JIRA Ticket
SDKS-2550
Description
Adding a README.md to the Token Vault project.
Type of Change
How Has This Been Tested?
No testing needed, but has been reviewed by multiple people.
Definition of Done
Check all that apply
Documentation