<?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>topic Re: Problems Using Self-Signed Certificates to Register Node in Network Access Control</title>
    <link>https://community.cisco.com/t5/network-access-control/problems-using-self-signed-certificates-to-register-node/m-p/3895673#M471237</link>
    <description>&lt;P&gt;Figured this out based on some of the description there.&amp;nbsp; The domain name I used during install locked in the self-signed cert so when I had to change the domain name because I later found out it was incorrect, this caused me problems.&amp;nbsp; I changed the domain name from the ISE command line, waited a few for new certs to generate, and imported those successfully and registered what I needed.&amp;nbsp; Thanks!&lt;/P&gt;</description>
    <pubDate>Tue, 23 Jul 2019 13:14:45 GMT</pubDate>
    <dc:creator>s1nsp4wn</dc:creator>
    <dc:date>2019-07-23T13:14:45Z</dc:date>
    <item>
      <title>Problems Using Self-Signed Certificates to Register Node</title>
      <link>https://community.cisco.com/t5/network-access-control/problems-using-self-signed-certificates-to-register-node/m-p/3895153#M471217</link>
      <description>&lt;P&gt;I'm trying to register a 2nd node into my ISE 2.4 deployment.&amp;nbsp; I get warned that the default self-signed device cert of the other ISE node is being offered and I click accept to trust it anyways.&amp;nbsp; I get the error&lt;/P&gt;
&lt;P style="padding-left: 30px;"&gt;&lt;FONT color="#FF6600"&gt;&lt;SPAN&gt;Unable to authenticate ISE &amp;lt;2nd-ISE-FQDN&amp;gt;. Please check certificate configuration.&lt;/SPAN&gt;&lt;/FONT&gt;&lt;/P&gt;
&lt;P style="padding-left: 30px;"&gt;&lt;FONT color="#FF6600"&gt;&lt;SPAN&gt;Make sure from ‘Primary Admin node’, system certificate chain of registering node is present in ‘Trusted certificates’ and is enabled with ‘Trust for authentication within ISE’ option selected.&lt;/SPAN&gt;&lt;/FONT&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Well I exported that cert from the I want to register into the PAN i'm registering from to trusted store and selected use with ISE option as asked and I'm still greeted with that error.&amp;nbsp; Is this no the recommended way?&amp;nbsp; I'm using the suggestions from Cisco's admin guides and lab minutes youtube videos.&lt;/P&gt;</description>
      <pubDate>Mon, 22 Jul 2019 23:04:59 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/problems-using-self-signed-certificates-to-register-node/m-p/3895153#M471217</guid>
      <dc:creator>s1nsp4wn</dc:creator>
      <dc:date>2019-07-22T23:04:59Z</dc:date>
    </item>
    <item>
      <title>Re: Problems Using Self-Signed Certificates to Register Node</title>
      <link>https://community.cisco.com/t5/network-access-control/problems-using-self-signed-certificates-to-register-node/m-p/3895196#M471227</link>
      <description>&lt;P&gt;The message is the same as reported in&amp;nbsp;CSCvd33544&lt;/P&gt;
&lt;P&gt;If possible, please open a TAC case, as our teams have not found a way to recreate it. And, one deployment had mismatched domain-name between what configured ISE admin CLI and shown in ISE admin web UI.&lt;/P&gt;</description>
      <pubDate>Mon, 22 Jul 2019 23:25:59 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/problems-using-self-signed-certificates-to-register-node/m-p/3895196#M471227</guid>
      <dc:creator>hslai</dc:creator>
      <dc:date>2019-07-22T23:25:59Z</dc:date>
    </item>
    <item>
      <title>Re: Problems Using Self-Signed Certificates to Register Node</title>
      <link>https://community.cisco.com/t5/network-access-control/problems-using-self-signed-certificates-to-register-node/m-p/3895673#M471237</link>
      <description>&lt;P&gt;Figured this out based on some of the description there.&amp;nbsp; The domain name I used during install locked in the self-signed cert so when I had to change the domain name because I later found out it was incorrect, this caused me problems.&amp;nbsp; I changed the domain name from the ISE command line, waited a few for new certs to generate, and imported those successfully and registered what I needed.&amp;nbsp; Thanks!&lt;/P&gt;</description>
      <pubDate>Tue, 23 Jul 2019 13:14:45 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/problems-using-self-signed-certificates-to-register-node/m-p/3895673#M471237</guid>
      <dc:creator>s1nsp4wn</dc:creator>
      <dc:date>2019-07-23T13:14:45Z</dc:date>
    </item>
  </channel>
</rss>

