AMBARI-26277:Fix kerberos encryption error, Update Supported Encryption Types in Kerberos Configuration #3926
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:
This PR updates the supported encryption types in the Kerberos configuration to enhance security and align with modern encryption standards. The current configuration includes outdated and less secure encryption types, which are replaced with stronger and more widely supported encryption algorithms.
Changes:
kerberos-env.xmlfile in theambari/ambari-server/src/main/resources/stacks/BIGTOP/3.2.0/services/KERBEROS/configuration/directory.Reason for Change:
des3-cbc-sha1,rc4, anddes-cbc-md5) are considered weak and vulnerable to attacks.aes256-cts-hmac-sha1-96andaes128-cts-hmac-sha1-96) are more secure and widely supported in modern Kerberos implementations.Impact:
ambari/ambari-server/src/main/resources/stacks/BIGTOP/3.2.0/services/KERBEROS/configuration/kerberos-env.xml

ambari/ambari-server/src/main/resources/stacks/BIGTOP/3.2.0/services/KERBEROS/properties/krb5_conf.j2
