You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ambari.apache.org by "Robert Levas (JIRA)" <ji...@apache.org> on 2017/06/02 20:30:04 UTC

[jira] [Updated] (AMBARI-20938) LDAPS connections to an Active Directory when enabling Kerberos should validate the server's SSL certificate

     [ https://issues.apache.org/jira/browse/AMBARI-20938?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Robert Levas updated AMBARI-20938:
----------------------------------
    Resolution: Fixed
        Status: Resolved  (was: Patch Available)

Committed to trunk
{noformat}
commit c3c06ea9889e0a462d67e8a765b41d0a4aead9b2
Author: Robert Levas <rl...@hortonworks.com>
Date:   Fri Jun 2 15:43:43 2017 -0400
{noformat}

Committed to branch-2.5
{noformat}
commit 4418358f8091d4d8ace19af186361762ad8aaa1d
Author: Robert Levas <rl...@hortonworks.com>
Date:   Fri Jun 2 15:41:00 2017 -0400
{noformat}


> LDAPS connections to an Active Directory when enabling Kerberos should validate the server's SSL certificate
> ------------------------------------------------------------------------------------------------------------
>
>                 Key: AMBARI-20938
>                 URL: https://issues.apache.org/jira/browse/AMBARI-20938
>             Project: Ambari
>          Issue Type: Bug
>          Components: ambari-server
>    Affects Versions: 2.0.0
>            Reporter: Robert Levas
>            Assignee: Robert Levas
>              Labels: active-directory, active_directory, kerberos, ssl
>             Fix For: 2.5.2
>
>         Attachments: AMBARI-20938_branch-2.5_01.patch, AMBARI-20938_trunk_01.patch
>
>
> LDAPS connections to an Active Directory when enabling Kerberos should validate the server's SSL certificate.  The current implementation skips validation checks to help avoid SSL issues; however this is not secure. Also the _trusting_ SSL connection may not support the more secure SSL protocols - TLSv1.2.
> A flag in the {{ambari.properties}} file ({{kerberos.operation.verify.kdc.trust}}) should be available to allow for the user to select either a _trusting_  SSL connection or a validating (non-trusting) SSL connection to be used.  The default should be to use the standard (non-trusting) SSL connection. 



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)