Mailing-List: contact dev-help@ambari.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@ambari.apache.org
Date: Mon, 29 Feb 2016 21:52:18 +0000 (UTC)
From: "Bolke de Bruin (JIRA)" <jira@apache.org>
To: dev@ambari.apache.org
Message-ID: <JIRA.12726312.1404909638000.176738.1456782738269@Atlassian.JIRA>
In-Reply-To: <JIRA.12726312.1404909638000@Atlassian.JIRA>
References: <JIRA.12726312.1404909638000@Atlassian.JIRA>
 <JIRA.12726312.1404909638865@arcas>
Subject: [jira] [Updated] (AMBARI-6432) FreeIPA Support in Ambari
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Bolke de Bruin updated AMBARI-6432:
-----------------------------------
    Attachment: AMBARI-6432.trunk.v2.patch

New version of the patch that addresses the issues mentioned on the review board.

* Code layout (2 vs 4)
* Better logging
* Try and catch separate for each stream
* Configurable timeout for the password chat
* Bugfix

> 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
>         Attachments: AMBARI-6432-FreeIPA.patch, AMBARI-6432.trunk.v1.patch, AMBARI-6432.trunk.v2.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)