<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>question Re: Enable Kerberos via Ambari Blueprint in Archives of Support Questions (Read Only)</title>
    <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/Enable-Kerberos-via-Ambari-Blueprint/m-p/125873#M31103</link>
    <description>&lt;A rel="user" href="https://community.cloudera.com/users/404/tveil.html" nodeid="404"&gt;@Tim Veil&lt;/A&gt;&lt;P&gt;Ambari will require kerberos admin principal in turn to create principals and keytabs for hadoop services. This is a pre-requisite that needs to be manually done.&lt;/P&gt;&lt;P&gt;An admin kdc credential can be created by manually executing following command:&lt;/P&gt;&lt;P&gt;kadmin.local -q 'addprinc -pw admin admin/admin'&lt;/P&gt;&lt;P&gt;Other pre-requisites include:&lt;/P&gt;&lt;P&gt;1) Existing and working KDC. &lt;/P&gt;&lt;P&gt;2) Install and configure Kerberos client on Ambari server&lt;/P&gt;&lt;P&gt;3) making sure the JCE policies are present on all hosts. This is taken care by ambari if user selects default option of Ambari provisioned JDK while setting up ambari-server. But if user selects custom JDK then user needs to make sure that JCE policies are present on all hosts.&lt;/P&gt;</description>
    <pubDate>Wed, 08 Jun 2016 08:22:04 GMT</pubDate>
    <dc:creator>jaimin</dc:creator>
    <dc:date>2016-06-08T08:22:04Z</dc:date>
    <item>
      <title>Enable Kerberos via Ambari Blueprint</title>
      <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/Enable-Kerberos-via-Ambari-Blueprint/m-p/125872#M31102</link>
      <description>&lt;P&gt;I'm trying to create an ambari blueprint that will provision a single node cluster using KERBEROS (see &lt;A href="https://issues.apache.org/jira/browse/AMBARI-13431" target="_blank"&gt;https://issues.apache.org/jira/browse/AMBARI-13431&lt;/A&gt; and &lt;A href="https://cwiki.apache.org/confluence/display/AMBARI/Blueprints#Blueprints-BlueprintExample:ProvisioningMulti-NodeHDP2.3ClustertouseKERBEROS"&gt;Ambari Blueprint Example&lt;/A&gt;).  My confusion is around the "credentials" block in the cluster creation template.  All available documentation includes this snippet:&lt;/P&gt;&lt;PRE&gt;"credentials" : [
     {
       "alias" : "kdc.admin.credential",
       "principal" : "admin/admin",
       "key" : "admin",
       "type" : "TEMPORARY"
     }
    ]
&lt;/PRE&gt;&lt;P&gt;My question is this... Are the principal and key (password) included above intended to describe &lt;EM&gt;&lt;STRONG&gt;new&lt;/STRONG&gt; &lt;/EM&gt;credentials (to be created/used by ambari) or &lt;EM&gt;&lt;STRONG&gt;existing&lt;/STRONG&gt; &lt;/EM&gt;credentials previously created by calling something like:&lt;/P&gt;&lt;PRE&gt;kadmin.local -q "addprinc admin/admin"&lt;/PRE&gt;&lt;P&gt;It boils down to what KERBEROS configuration is required before using Blueprints to install and configure the cluster.  In otherwords, how much of &lt;A href="http://docs.hortonworks.com/HDPDocuments/Ambari-2.2.2.0/bk_Ambari_Security_Guide/content/_optional_install_a_new_mit_kdc.html"&gt;this&lt;/A&gt; should be done before creating the cluster via blueprints. &lt;/P&gt;</description>
      <pubDate>Wed, 08 Jun 2016 08:10:06 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Archives-of-Support-Questions/Enable-Kerberos-via-Ambari-Blueprint/m-p/125872#M31102</guid>
      <dc:creator>tveil</dc:creator>
      <dc:date>2016-06-08T08:10:06Z</dc:date>
    </item>
    <item>
      <title>Re: Enable Kerberos via Ambari Blueprint</title>
      <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/Enable-Kerberos-via-Ambari-Blueprint/m-p/125873#M31103</link>
      <description>&lt;A rel="user" href="https://community.cloudera.com/users/404/tveil.html" nodeid="404"&gt;@Tim Veil&lt;/A&gt;&lt;P&gt;Ambari will require kerberos admin principal in turn to create principals and keytabs for hadoop services. This is a pre-requisite that needs to be manually done.&lt;/P&gt;&lt;P&gt;An admin kdc credential can be created by manually executing following command:&lt;/P&gt;&lt;P&gt;kadmin.local -q 'addprinc -pw admin admin/admin'&lt;/P&gt;&lt;P&gt;Other pre-requisites include:&lt;/P&gt;&lt;P&gt;1) Existing and working KDC. &lt;/P&gt;&lt;P&gt;2) Install and configure Kerberos client on Ambari server&lt;/P&gt;&lt;P&gt;3) making sure the JCE policies are present on all hosts. This is taken care by ambari if user selects default option of Ambari provisioned JDK while setting up ambari-server. But if user selects custom JDK then user needs to make sure that JCE policies are present on all hosts.&lt;/P&gt;</description>
      <pubDate>Wed, 08 Jun 2016 08:22:04 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Archives-of-Support-Questions/Enable-Kerberos-via-Ambari-Blueprint/m-p/125873#M31103</guid>
      <dc:creator>jaimin</dc:creator>
      <dc:date>2016-06-08T08:22:04Z</dc:date>
    </item>
    <item>
      <title>Re: Enable Kerberos via Ambari Blueprint</title>
      <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/Enable-Kerberos-via-Ambari-Blueprint/m-p/125874#M31104</link>
      <description>&lt;A rel="user" href="https://community.cloudera.com/users/404/tveil.html" nodeid="404"&gt;@Tim Veil&lt;/A&gt; you might find this post helpful as a reference, or to integrate into your project:&lt;P&gt;&lt;A href="https://community.hortonworks.com/articles/29203/automated-kerberos-installation-and-configuration.html" target="_blank"&gt;https://community.hortonworks.com/articles/29203/automated-kerberos-installation-and-configuration.html&lt;/A&gt;&lt;/P&gt;</description>
      <pubDate>Thu, 09 Jun 2016 01:19:51 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Archives-of-Support-Questions/Enable-Kerberos-via-Ambari-Blueprint/m-p/125874#M31104</guid>
      <dc:creator>amiller</dc:creator>
      <dc:date>2016-06-09T01:19:51Z</dc:date>
    </item>
    <item>
      <title>Re: Enable Kerberos via Ambari Blueprint</title>
      <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/Enable-Kerberos-via-Ambari-Blueprint/m-p/125875#M31105</link>
      <description>&lt;P&gt;This was the hint I needed.  &lt;A target="_blank" href="https://github.com/timveil/hdp-vagrant-generator/blob/master/examples/kerberos/Vagrantfile"&gt;Here&lt;/A&gt; is a link to the Vagrantfile I used to test.  It includes both the Kerberos command prerequisites and the Ambari Blueprint with related calls.  The key, for me, was ensuring this was run before creating submitting the blueprint.&lt;/P&gt;&lt;PRE&gt;# make sure Kerberos packages are installed
yum install krb5-libs krb5-server krb5-workstation -y

# modify Kerberos files
sed -i "s/kerberos.example.com/hdp-common-secure.hdp.local/gI" /etc/krb5.conf
sed -i "s/EXAMPLE.COM/hdp.local/gI" /etc/krb5.conf
sed -i "s/#//g" /etc/krb5.conf
sed -i "s/EXAMPLE.COM/hdp.local/gI" /var/kerberos/krb5kdc/kadm5.acl

# create Kerberos database and add principal.  "Bbh2z8HrVx" is my master password
kdb5_util create -s -P Bbh2z8HrVx
kadmin.local -q 'addprinc -pw admin admin/admin' -w Bbh2z8HrVx

# start and enable Kerberos services
systemctl start krb5kdc
systemctl enable krb5kdc
systemctl start kadmin
systemctl enable kadmin
&lt;/PRE&gt;</description>
      <pubDate>Fri, 10 Jun 2016 02:10:00 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Archives-of-Support-Questions/Enable-Kerberos-via-Ambari-Blueprint/m-p/125875#M31105</guid>
      <dc:creator>tveil</dc:creator>
      <dc:date>2016-06-10T02:10:00Z</dc:date>
    </item>
  </channel>
</rss>

