Additional information in the log output when an InvalidCipherException occurs.#2334
Merged
ryanjbaxter merged 2 commits intospring-cloud:mainfrom Oct 18, 2023
Conversation
kworkbee
changed the title
kworkbee
commented
Sep 30, 2023
ryanjbaxter
requested changes
Oct 17, 2023
Contributor
Author
|
@ryanjbaxter I fixed the message. |
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
3 participants
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.
When a client application is starting with a mismatch symmetric key (between client and server), the output log prints before InvalidCipherException is thrown due to un-decryptable configuration properties, which creates additional information with log message because the message alone lacks information to guess why the InvalidCipherException occurred.
Relates to #1386