-
Notifications
You must be signed in to change notification settings - Fork 3
Update nav structure for Docs Authentication section, add info on OAuth key injection flow #282
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
Conversation
fern/products/docs/pages/api-references/autopopulate-api-key.mdx
Outdated
Show resolved
Hide resolved
| <Accordion title="OAuth" toc={true}> | ||
|
|
||
| ### How it works | ||
|
|
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.
maybe could link to the rbac page diagram to point the user to a visual?
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 just did this, but thinking about this more, I'm wondering if the diagrams would be a better fit on the key injection page, just because that is where the detailed information about the two ways is. And then we could add a pointer to the rbac page. Wdyt? @chdeskur
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 ended up doing this, and added a bit about the OAuth flow to the RBAC page. I tried to reorganize so the bulk of the jwt vs oauth flow is in one place, the API Key Injection page. Let me know what you think!
No description provided.