Add clarification to clerk as IDP docs page #2082
Merged
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.
🔎 Previews:
What does this solve?
We have had many users come across the "Clerk as an OAuth2/OIDC IDP" feature and reasonably assume that this meant that Clerk will run a full OAuth2 server for your app which handles not only initial authentication, but also handles subsequent request authorization to API endpoints within your application.
What changed?
At the moment, this feature only handles initial authentication, and that was not clear in the docs, so I added a section to clarify this.
Checklist