[
https://issues.apache.org/jira/browse/AMBARI-6432?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15187289#comment-15187289
]
Robert Levas commented on AMBARI-6432:
--------------------------------------
[~u39kun], [~bolke]... The issue is not limited to the test identity. All
headless identities, by default, append the cluster name in order to generate a
unique name in the even multiple clusters share the same KDC.
A possible solution could be to add a new _function_ to the variable
replacement facility to convert perform a "to lower" operation on the value -
see org.apache.ambari.server.state.kerberos.VariableReplacementHelper.
If we go that route, the cluster name placeholder can be changed to look like:
{code}
${cluster_name|toLower}
{code}
Or we can add a new kerberos-env property to set all principal names to
lowercase - {{kerberos-env/force_lowercase_principal_names}}. Then generate the
principal names as needed - there may be several places that we need to do this
or maybe perform and operation on the Kerberos Descriptor before we do any work
with it.
> FreeIPA Support in Ambari
> -------------------------
>
> Key: AMBARI-6432
> URL: https://issues.apache.org/jira/browse/AMBARI-6432
> Project: Ambari
> Issue Type: Improvement
> Components: ambari-server
> Affects Versions: trunk
> Reporter: jay vyas
> Assignee: Bolke de Bruin
> Fix For: 2.4.0
>
> Attachments: AMBARI-6432-FreeIPA.patch, AMBARI-6432.patch,
> AMBARI-6432.trunk.v1.patch, AMBARI-6432.trunk.v2.patch,
> AMBARI-6432.trunk.v3.patch, AMBARI-6432.trunk.v4.patch,
> AMBARI-6432.trunk.v5.patch, AMBARI-6432.trunk.v5.patch, ipa-patch-v0.5.patch
>
>
> FreeIPA Is a powerful tool for unifying identity, kerberos credentials,
> across a cluster.
> A great value add for ambari would be to provide support for using FreeIPA to
> kerberize services. This would allow for
> 1) better HCFS interoperability, because first class GID/UID is critical for
> certain file systems (GlusterFS, Lustre, and any other file system which uses
> kernel / FUSE apis for determining identity)
> 2) better enterprise interoperability. Because of the fact that FreeIPA
> makes it easy to interop with different identity solutions (like active
> directory), it would make ambari easier to adopt for various enterprises.
> 3) broadens ambaris scope. Now ambari could also allow people to setup the
> users of their clusters, and at least some of the security features of their
> clusters, all from one interface (no more manual handling of TGTs and such -
> it could all be done quite easily via the ambari UI which could make calls to
> underlying FreeIPA clients).
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
