fix (kubernetes-client-api) : OpenIDConnectionUtils uses caCertFile and caCertData as a fallback option when idp-certificate-authority-data
is not specified
#5818
+47
−1
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
Fix #5817
Currently, we fall back to caCertData specified in Config when
idp-certificate-authority-data
is not specified. We should also consider reading cert data from caCertFile. From discussion in redhat-developer/intellij-kubernetes#726 , user had cert data specified incaCertFile
The fix was tested by @adietish in build of IntelliJ Plugin and it seems to fix the issue for the user #5817 (comment)
I have tested the token refresh flow on EKS cluster (thanks to @adietish) , it seems to be working.
Type of change
test, version modification, documentation, etc.)
Checklist