User secret management #135
Merged
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
sujen1412
requested changes
Aug 14, 2024
Co-authored-by: Sujen Shah <[email protected]>
…ions error handling; minor refactoring
|
|
@sujen1412 the admin role restriction for pre_approved_email endpoints and improved exception handling is ready for final review. |
sujen1412
approved these changes
Aug 19, 2024
Merged
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.
Add support for creating and retrieving user secrets within MAAP for use inside algorithms. See ticket: MAAP-Project/Community#1048
Changes:
cryptographylibrary for encrypting secret values. Encrypted secrets are stored in a newmember_secrettable.api/membernamespaces to move admin-specific endpoints into a newapi/adminnamespace.