[
https://issues.apache.org/jira/browse/AMBARI-14628?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tom Beerbower updated AMBARI-14628:
-----------------------------------
Attachment: AMBARI-14628.patch
> Create JAAS config for Atlas.
> -----------------------------
>
> Key: AMBARI-14628
> URL: https://issues.apache.org/jira/browse/AMBARI-14628
> Project: Ambari
> Issue Type: Improvement
> Reporter: Tom Beerbower
> Assignee: Tom Beerbower
> Attachments: AMBARI-14628.patch
>
>
> Ideally, Ambari would create the JAAS config for Atlas automatically when the
> cluster is Kerberized.
> When Atlas is configured with HBase as the storage backend in a secure
> cluster, a JAAS configuration file should be created and specified so that
> the HBase client can attempt to SASL-authenticate.
> Create Atlas JAAS configuration file (e.g. /etc/atlas/conf/atlas-jaas.conf).
> {code}
> Client {
> com.sun.security.auth.module.Krb5LoginModule required
> useKeyTab=true
> useTicketCache=false
> storeKey=true
> doNotPrompt=false
> keyTab="<atlas keytab>"
> principal="<atlas principal>";
> };
> {code}
> Update Atlas METADATA_OPTS to include ‘java.security.auth.login.config’ set
> to the above Atlas JAAS configuration file.
> For example,
> {{-Djava.security.auth.login.config=/etc/atlas/conf/atlas-jaas.conf}}.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
