feat(web): manage access policies on native API keys - #478
Draft
linonetwo wants to merge 2 commits into
Draft
Conversation
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
1 participant
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.
Summary
Adds an optional Access & quotas action to the existing CPA native api-keys card. It does not add another key list or issue a second downstream key. The modal binds policy by the existing key's SHA-256 and configures provider/model grants plus request/token quotas through the plugin Management API.
Motivation
A policy plugin that creates its own keys duplicates CPA's native authentication and CPAMP aliases. Operators then have to synchronize two identities and plaintext keys. The desired model is:
API
Uses cpa-key-policy native-access endpoints:
Provider and model values support exact names plus * and ? wildcards. UI and external automation share the same API.
Compatibility
The action is additive and only appears as an optional integration. Includes zh-CN, zh-TW, en and ru strings. The backend work is tracked in origin652/cpa-plugin-key-policy#6 and model catalog filtering in router-for-me/CLIProxyAPI#4766.