feat(custodian): add support for authorization for accessing keys #24
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
Chethan-rao
suggested changes
Oct 5, 2024
dracarys18
suggested changes
Oct 7, 2024
| ) -> errors::CustomResult<DecryptedDataGroup, errors::CryptoError> { | ||
| let version = FxHashSet::from_iter(self.0.values().map(|d| d.version)); | ||
| let decrypted_keys = Key::get_multiple_keys(state, identifier, version) | ||
| .await | ||
| .switch()?; | ||
|
|
||
| let mut stored_tokens = decrypted_keys.values().map(|k| &k.token); |
There was a problem hiding this comment.
Suggested change
| let mut stored_tokens = decrypted_keys.values().map(|k| &k.token); | |
| let stored_tokens = decrypted_keys.values().map(|k| &k.token); |
There was a problem hiding this comment.
It's required, as it's a opaque type that will be acted upon: when we call .all on it
Chethan-rao
reviewed
Oct 7, 2024
|
Sure looks good to me, please test it once |
dracarys18
approved these changes
Oct 9, 2024
Chethan-rao
approved these changes
Oct 9, 2024
Willem-Barkhuizen
added a commit
to Willem-Barkhuizen/hyperswitch-helm
that referenced
this pull request
Jun 30, 2025
\#### Summary This commit adds the required secrets supporting the changes made to the `hyperswitch-encryption-service` package in the following two PRs: * [feat(custodian): add support for authorization for accessing keys](juspay/hyperswitch-encryption-service#24) * [refactor: kms encrypt blake3 hash key](juspay/hyperswitch-encryption-service#35) \#### Testing Pointed our local CDK package, also containing changes to be PR'ed, at this chart and the resultant `keymanager` pod launched successfully. Some extracts: * `keymanager-secrets-hs-keymanager` Secret ``` apiVersion: v1 data: CRIPTA__CERTS__ROOT_CA: CRIPTA__CERTS__TLS_CERT: <SECRET> CRIPTA__CERTS__TLS_KEY: <SECRET> CRIPTA__SECRETS__ACCESS_TOKEN: <SECRET> CRIPTA__SECRETS__HASH_CONTEXT: <SECRET> CRIPTA__SECRETS__KMS_CONFIG__KEY_ID: <SECRET> CRIPTA__SECRETS__KMS_CONFIG__REGION: <SECRET> kind: Secret metadata: annotations: ... type: Opaque ``` * `keymanager-hs-keymanager-<ID>` Pod ``` apiVersion: v1 kind: Pod metadata: creationTimestamp: "2025-06-27T17:48:56Z" generateName: keymanager-hs-keymanager-<ID> ... uid: <UID> spec: containers: - env: ... - name: CRIPTA__SECRETS__ACCESS_TOKEN valueFrom: secretKeyRef: key: CRIPTA__SECRETS__ACCESS_TOKEN name: keymanager-secrets-hs-keymanager - name: CRIPTA__SECRETS__HASH_CONTEXT valueFrom: secretKeyRef: key: CRIPTA__SECRETS__HASH_CONTEXT name: keymanager-secrets-hs-keymanager ... ``` * `keymanager` Pod logs ``` {"timestamp":"2025-06-27T17:49:10.256534Z","level":"INFO","fields":{"message":"Application starting [Server { port: 5000, host: \"0.0.0.0\" }...} {"timestamp":"2025-06-27T17:49:10.578842Z","level":"INFO","fields":{"message":"Metrics Server started at [Server { port: 6128, host: \"0.0.0.0\" }]"},"target":"cripta"} ``` --- Signed-Off-By: Willem Barkhuizen (<[email protected]>)
Willem-Barkhuizen
added a commit
to Willem-Barkhuizen/hyperswitch-helm
that referenced
this pull request
Jun 30, 2025
\#### Summary This commit adds the required secrets supporting the changes made to the `hyperswitch-encryption-service` package in the following two PRs: * [feat(custodian): add support for authorization for accessing keys](juspay/hyperswitch-encryption-service#24) * [refactor: kms encrypt blake3 hash key](juspay/hyperswitch-encryption-service#35) \#### Testing Pointed our local CDK package, also containing changes to be PR'ed, at this chart and the resultant `keymanager` pod launched successfully. Some extracts: * `keymanager-secrets-hs-keymanager` Secret ``` apiVersion: v1 data: CRIPTA__CERTS__ROOT_CA: CRIPTA__CERTS__TLS_CERT: <SECRET> CRIPTA__CERTS__TLS_KEY: <SECRET> CRIPTA__SECRETS__ACCESS_TOKEN: <SECRET> CRIPTA__SECRETS__HASH_CONTEXT: <SECRET> CRIPTA__SECRETS__KMS_CONFIG__KEY_ID: <SECRET> CRIPTA__SECRETS__KMS_CONFIG__REGION: <SECRET> kind: Secret metadata: annotations: ... type: Opaque ``` * `keymanager-hs-keymanager-<ID>` Container ``` apiVersion: v1 kind: Pod metadata: creationTimestamp: "2025-06-27T17:48:56Z" generateName: keymanager-hs-keymanager-<ID> ... uid: <UID> spec: containers: - env: ... - name: CRIPTA__SECRETS__ACCESS_TOKEN valueFrom: secretKeyRef: key: CRIPTA__SECRETS__ACCESS_TOKEN name: keymanager-secrets-hs-keymanager - name: CRIPTA__SECRETS__HASH_CONTEXT valueFrom: secretKeyRef: key: CRIPTA__SECRETS__HASH_CONTEXT name: keymanager-secrets-hs-keymanager ... ``` * `keymanager` Pod logs ``` {"timestamp":"2025-06-27T17:49:10.256534Z","level":"INFO","fields":{"message":"Application starting [Server { port: 5000, host: \"0.0.0.0\" }...} {"timestamp":"2025-06-27T17:49:10.578842Z","level":"INFO","fields":{"message":"Metrics Server started at [Server { port: 6128, host: \"0.0.0.0\" }]"},"target":"cripta"} ``` --- Signed-Off-By: Willem Barkhuizen (<[email protected]>)
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.
Description
Adding custodian support. Adding support for Basic authentication on top of mTLS, to make sure that the keys being accessed belong to the respective party.