Register new scope 'cody_gateway::flaggedprompts::*' #11
Conversation
This file contains 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.
As part of some work I'm doing with battling abuse in Cody Gateway, I registered a new SAMS-authenticated REST API https://github.com/sourcegraph/sourcegraph/pull/61514/files. This new REST API performs authentication by looking for the
"cody_gateway::flaggedprompts::read"scope.No SAMS clients have that scope yet. Nor can I register one until after merging this PR and getting it integrated into
Sourcegraph-accounts, and then deploying that to production.... but once that is done, I'll register a new SAMS Client for
abuse-ban-bot, and add that as one of the scopes the client is able to request. Thereby allowing to be make use of these new APIs.Test plan
NA