[
https://issues.apache.org/jira/browse/AMBARI-18813?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Levas updated AMBARI-18813:
----------------------------------
Fix Version/s: (was: 2.4.2)
2.5.0
> Optionally force username from LDAP authentication data to be lowercase in
> Ambari
> ---------------------------------------------------------------------------------
>
> Key: AMBARI-18813
> URL: https://issues.apache.org/jira/browse/AMBARI-18813
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
> Affects Versions: 2.4.0
> Reporter: Robert Levas
> Assignee: Robert Levas
> Labels: ldap
> Fix For: 2.5.0
>
>
> Optionally force username from LDAP authentication data to be lowercase in
> Ambari based on LDAP import configuration.
> In some cases the username declared in the relevant LDAP object is in all
> uppercase characters when the local Hadoop cluster expects the username to be
> all lowercase. As of Ambari 2.4.0, the username specified from the LDAP data
> is used to override the username known to Ambari. This overwritten data may
> be in all uppercase characters, potentially breaking local username
> conventions.
> To help this scenario, provide a configuration option to force the username
> obtained from the LDAP object to be converted to all lowercase character.
> For example {{authentication.ldap.usernameAttribute.forceLowercase}}.
> This optional configuration value is to default to false to maintain current
> functionality.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
