feat(api-keys): allow copying saved active keys - #239
Closed
JnyRoad wants to merge 1 commit into
Closed
Conversation
Persist encrypted recovery copies across account, employee, and public API key lifecycles. Add authorized active-key reveal endpoints, SQLite compatibility migration, and copy controls for the two management dialogs. Legacy and revoked keys remain unrecoverable. Tests: pytest backend/tests/test_public_api_v1.py backend/tests/test_database_config.py; npm dialog tests; i18n/config checks; production build.
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 owner- and manager-authorized reveal endpoint for active API keys, encrypted recovery copies created and refreshed on create/rotate, clearing on revoke, and account/employee console copy actions with legacy-key rotation guidance. Tests: backend pytest (33 passed); frontend Vitest (247 passed); production build; config check; import-order check. Note: upstream i18n check still reports an unrelated missing English translation in frontend-enterprise/src/pages/chat/chatHelpers.tsx, which this PR does not modify.