<?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: invalid KDC administrator credentials after upgrading ambari to 2.7.3 in Support Questions</title>
    <link>https://community.cloudera.com/t5/Support-Questions/invalid-KDC-administrator-credentials-after-upgrading-ambari/m-p/242803#M204602</link>
    <description>&lt;P&gt;&lt;A rel="user" href="https://community.cloudera.com/users/62296/scott1.html" nodeid="62296"&gt;@scott powers&lt;/A&gt;&lt;/P&gt;&lt;P&gt;As of Ambari 2.7, Ambari authenticates with an MIT KDC more securely - using Kerberos.  To do this, it must call kinit and specify the kadmin service principal.  &lt;/P&gt;&lt;PRE&gt;kinit -c &amp;lt;path&amp;gt; -S kadmin/&amp;lt;kadmin server FQDN&amp;gt;@&amp;lt;realm&amp;gt; &amp;lt;principal&amp;gt;&lt;/PRE&gt;&lt;P&gt;There may be one of two issue a play causing you an issue.&lt;/P&gt;&lt;P&gt;1) The KDC Administrator host is not set to the FQDN of the host there the kadmin server is running&lt;/P&gt;&lt;P&gt;2) The KDC does not have a principal like kadmin/&amp;lt;kadmin server FQDN&amp;gt;@&amp;lt;realm&amp;gt;&lt;/P&gt;&lt;P&gt;Fixing #1 may be done by editing the Kerberos service configurations via Ambari.  After restarting the Kerberos service, you should be able to properly kinit. &lt;/P&gt;&lt;P&gt;Fixing #2 may be done by adding the missing principal (kadmin/&amp;lt;kadmin server FQDN&amp;gt;@&amp;lt;realm&amp;gt;) to the MIT KDC.&lt;/P&gt;&lt;P&gt;In future versions of Ambari, you will be able to configure what the kadmin service principal is.  However for now, Ambari assumes it is kadmin/&amp;lt;kadmin server FQDN&amp;gt;@&amp;lt;realm&amp;gt;.  &lt;/P&gt;&lt;P&gt;If one of these solutions does not help, you should take a look at your ambari-server.log file and see if there are any interesting error messages posted that you can share here. &lt;/P&gt;</description>
    <pubDate>Thu, 24 Jan 2019 00:19:29 GMT</pubDate>
    <dc:creator>rlevas</dc:creator>
    <dc:date>2019-01-24T00:19:29Z</dc:date>
    <item>
      <title>invalid KDC administrator credentials after upgrading ambari to 2.7.3</title>
      <link>https://community.cloudera.com/t5/Support-Questions/invalid-KDC-administrator-credentials-after-upgrading-ambari/m-p/242802#M204601</link>
      <description>&lt;P&gt;I just upgraded ambari to 2.7.3 on my cluster.  The cluster had previously been configured with kerberos, and running correctly.  Now whenever I try to modify components I get an "admin session expired" dialog.  I enter my admin credentials (kerberos) and get an invalid KDC admin error returned.  I verified that the principal I entered has admin rights by logging into kadmin on the command line.  The principal I am entering is the one I used when I initially configured the cluster to use kerberos.  Why would this not work anymore, and how can I fix it?  &lt;/P&gt;</description>
      <pubDate>Wed, 23 Jan 2019 23:54:38 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Support-Questions/invalid-KDC-administrator-credentials-after-upgrading-ambari/m-p/242802#M204601</guid>
      <dc:creator>scott1</dc:creator>
      <dc:date>2019-01-23T23:54:38Z</dc:date>
    </item>
    <item>
      <title>Re: invalid KDC administrator credentials after upgrading ambari to 2.7.3</title>
      <link>https://community.cloudera.com/t5/Support-Questions/invalid-KDC-administrator-credentials-after-upgrading-ambari/m-p/242803#M204602</link>
      <description>&lt;P&gt;&lt;A rel="user" href="https://community.cloudera.com/users/62296/scott1.html" nodeid="62296"&gt;@scott powers&lt;/A&gt;&lt;/P&gt;&lt;P&gt;As of Ambari 2.7, Ambari authenticates with an MIT KDC more securely - using Kerberos.  To do this, it must call kinit and specify the kadmin service principal.  &lt;/P&gt;&lt;PRE&gt;kinit -c &amp;lt;path&amp;gt; -S kadmin/&amp;lt;kadmin server FQDN&amp;gt;@&amp;lt;realm&amp;gt; &amp;lt;principal&amp;gt;&lt;/PRE&gt;&lt;P&gt;There may be one of two issue a play causing you an issue.&lt;/P&gt;&lt;P&gt;1) The KDC Administrator host is not set to the FQDN of the host there the kadmin server is running&lt;/P&gt;&lt;P&gt;2) The KDC does not have a principal like kadmin/&amp;lt;kadmin server FQDN&amp;gt;@&amp;lt;realm&amp;gt;&lt;/P&gt;&lt;P&gt;Fixing #1 may be done by editing the Kerberos service configurations via Ambari.  After restarting the Kerberos service, you should be able to properly kinit. &lt;/P&gt;&lt;P&gt;Fixing #2 may be done by adding the missing principal (kadmin/&amp;lt;kadmin server FQDN&amp;gt;@&amp;lt;realm&amp;gt;) to the MIT KDC.&lt;/P&gt;&lt;P&gt;In future versions of Ambari, you will be able to configure what the kadmin service principal is.  However for now, Ambari assumes it is kadmin/&amp;lt;kadmin server FQDN&amp;gt;@&amp;lt;realm&amp;gt;.  &lt;/P&gt;&lt;P&gt;If one of these solutions does not help, you should take a look at your ambari-server.log file and see if there are any interesting error messages posted that you can share here. &lt;/P&gt;</description>
      <pubDate>Thu, 24 Jan 2019 00:19:29 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Support-Questions/invalid-KDC-administrator-credentials-after-upgrading-ambari/m-p/242803#M204602</guid>
      <dc:creator>rlevas</dc:creator>
      <dc:date>2019-01-24T00:19:29Z</dc:date>
    </item>
  </channel>
</rss>

