Add Base64 encoding support for SecretEncryptionConfiguration#2125
Open
MariusVolkhart wants to merge 1 commit intomicronaut-projects:4.16.xfrom
Open
Add Base64 encoding support for SecretEncryptionConfiguration#2125MariusVolkhart wants to merge 1 commit intomicronaut-projects:4.16.xfrom
MariusVolkhart wants to merge 1 commit intomicronaut-projects:4.16.xfrom
Conversation
Mirrors the base64 encoding functionality that exists in SecretSignatureConfiguration to SecretEncryptionConfiguration, allowing JWT encryption secrets to be supplied as Base64-encoded strings. Changes: - Add base64 field with getter/setter to SecretEncryptionConfiguration - Modify SecretEncryption constructor to decode Base64 secrets when the base64 flag is set (default: false) - Add comprehensive integration tests (JwtEncryptionBase64Spec) covering Base64 encoding, decryption, and backward compatibility - Add documentation (jwtEncryptionSecret.adoc) with examples of both plain text and Base64-encoded secret configuration - Update SecretEncryptionSpec with YAML configuration example All examples use A256GCM encryption method with dir (direct) algorithm for modern AEAD-based encryption. Backward compatibility is fully maintained with base64 defaulting to false. Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>
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.
Mirrors the base64 encoding functionality that exists in
SecretSignatureConfigurationtoSecretEncryptionConfiguration, allowing JWT encryption secrets to be supplied as Base64-encoded strings.Changes:
SecretEncryptionConfigurationSecretEncryptionconstructor to decode Base64 secrets when the base64 flag is set (default: false)JwtEncryptionBase64Spec) covering Base64 encoding, decryption, and backward compatibilitySecretEncryptionSpecwith YAML configuration exampleAll examples use A256GCM encryption method with dir (direct) algorithm for modern AEAD-based encryption.
Backward compatibility is fully maintained with base64 defaulting to false.