[AMBARI-24447] No subject alternative DNS name exception encountered when Enabling Kerberos against an Active Directory even when SSL verification is off #2012
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.
What changes were proposed in this pull request?
No subject alternative DNS name exception encountered when Enabling Kerberos against an Active Directory even when SSL verification is off.
Note: This occurs when the hostname embedded in the SSL certificate does not match the hostname of the Active Directory host and Open JDK 1.8.181-b13 is used. This is not seen when Oracle JDK is used.
Observed with this version of JDK:
Not observed with this version of JDK
Solution
The
org.apache.ambari.server.security.InternalSSLSocketFactory.LenientTrustManager
class needs to extendjavax.net.ssl.X509ExtendedTrustManager
and do nothing in the additional overridden methods.How was this patch tested?
Manually tested.
Please review Ambari Contributing Guide before opening a pull request.