[
https://issues.apache.org/jira/browse/AMBARI-9209?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Levas updated AMBARI-9209:
---------------------------------
Attachment: AMBARI-9209_01.patch
* Added
{{org.apache.ambari.server.serveraction.kerberos.DeconstructedPrincipal}} to
help parse and normalize principals
* Added {{principal_digest}} to the set of Velocity template variables. This
value is the binhexed MD5Hash of the normalized principal value
*Added and updated unit tests
Patch File [^AMBARI-9209_01.patch]
> Add the ability to append a random value to values in LDAP attributes when
> generating principals in Active Directory
> --------------------------------------------------------------------------------------------------------------------
>
> Key: AMBARI-9209
> URL: https://issues.apache.org/jira/browse/AMBARI-9209
> Project: Ambari
> Issue Type: Task
> Components: ambari-server
> Affects Versions: 2.0.0
> Reporter: Robert Levas
> Assignee: Robert Levas
> Labels: active_directory, kerberos
> Fix For: 2.0.0
>
> Attachments: AMBARI-9209_01.patch
>
>
> Add ability to append a random value to values in LDAP attributes when
> generating principals in Active Directory.
> For example the {{cn}} and {{sAMAccountName}} attributes must be unique. In
> some caes the {{cn}} is not allowed to have {{/}} characters and in all cases
> the {{sAMAccountName}} is not allow to have {{/}} characters. Therefore to
> generate values for these attributes, the _instance_ part of the principal
> needs to be stripped off and a random string needs to be appended.
> This can be seen where the principal is
> {{nn/[email protected]}}. The {{cn}} would typically be
> {{nn/c6501.ambari.apache.org}}. Providing for a random string would allow
> the {{cn}} value to be something like {{nn-ythnskdtarsjko5fsdfdsb}}. Since
> the {{sAMAccountName}} can be at most 20 characters, it would be
> {{nn-ythnskdtarsjko5fs}}.
> Since the generation of the attributes and values is done using a Velocity
> template, this random string will need to be generated and stored in the
> Velocity engine context before processing the template.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
