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

Sandor Molnar resolved AMBARI-25141.
------------------------------------
    Resolution: Fixed

My changes have been merged to {{branch-2.7}}:

 
{noformat}
$ git s
On branch branch-2.7
Your branch is up to date with 'upstream/branch-2.7'.
nothing to commit, working tree clean
$ git log
...
commit a05bb201067f0ae10d40f180bb6216d098f9447f
Author: Sandor Molnar <[email protected]>
Date: Mon Feb 4 17:37:33 2019 +0100
AMBARI-25141. Encrypting LDAP manager password in case password security is ON 
(#2810)
{noformat}
 

> LDAP password in cleartext in ldap-password.dat file after encrypting 
> passwords
> -------------------------------------------------------------------------------
>
>                 Key: AMBARI-25141
>                 URL: https://issues.apache.org/jira/browse/AMBARI-25141
>             Project: Ambari
>          Issue Type: Bug
>          Components: ambari-server
>    Affects Versions: 2.7.3
>            Reporter: Sandor Molnar
>            Assignee: Sandor Molnar
>            Priority: Critical
>              Labels: pull-request-available
>             Fix For: 2.7.4
>
>          Time Spent: 0.5h
>  Remaining Estimate: 0h
>
> In 2.7.x we store LDAP password within its own file; however the content of 
> that file is not encrypted even if password encryption is on. To approach 
> this issue the following should be done:
>  - in case password encryption is enabled we will encrypt the LDAP password 
> in the credential store and write the corresponding CS alias in the LDAP 
> password file (just like we do with other passwords in {{ambari.properties}})
>  - in case the password encryption is disabled we will write the raw password 
> in the LDAP password file
> In both cases an additional level of security can be achieved by setting the 
> appropriate user/group access on the file system to the LDAP password file.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to