KNOX-3311: Fix X509CertificateUtil.fetchPublicCertsFromServer issue w…#1217
Merged
hanicz merged 2 commits intoapache:masterfrom Apr 29, 2026
Merged
KNOX-3311: Fix X509CertificateUtil.fetchPublicCertsFromServer issue w…#1217hanicz merged 2 commits intoapache:masterfrom
hanicz merged 2 commits intoapache:masterfrom
Conversation
…here default truststore can't be loaded due to invalid/missing password
Test Results21 tests 21 ✅ 1s ⏱️ Results for commit fb2c342. ♻️ This comment has been updated with latest results. |
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
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.
…here default truststore can't be loaded due to invalid/missing password
KNOX-3311 - Fix X509CertificateUtil.fetchPublicCertsFromServer issue where default truststore can't be loaded due to invalid/missing password
What changes were proposed in this pull request?
Fix X509CertificateUtil.fetchPublicCertsFromServer issue where default truststore can't be loaded due to invalid/missing password
How was this patch tested?
Tested on FIPS cluster with BCFKS default truststore
Tested locally where the password is not set
Integration Tests
N/A
UI changes
N/A