Fix contradiction in API documentation regarding Client Credentials scopes#12631
Merged
notbakaneko merged 5 commits intoppy:masterfrom Jan 13, 2026
Merged
Conversation
4d7aa3f to
32f26ff
Compare
notbakaneko
requested changes
Jan 3, 2026
Co-authored-by: bakaneko <notbakaneko@users.noreply.github.com>
notbakaneko
approved these changes
Jan 13, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Fixes #12611
Documentation currently claims that
publicis the only meaningful scope for Client Credentials, which is misleadingIn reality, scopes like
delegate,forum.write_manage, andgroup_permissionsare supported and used by bots. I've updated the description to list these and added a note that delegatable scopes can't be mixed withpublicin a single requestThis was also recently discussed in openiddict-core #2403