<?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 Technically you can use ISE in Network Access Control</title>
    <link>https://community.cisco.com/t5/network-access-control/ise-ca-certificates/m-p/3053734#M22733</link>
    <description>&lt;P&gt;Technically you can use ISE as a CA. However, this is not recommended because most likely it will not scale.&lt;/P&gt;
&lt;P&gt;What is not clear to me is why you are trying to export the root certificate and private key and import it to another CA. Can you add more details?&lt;/P&gt;
&lt;P&gt;@berna_tllz&lt;/P&gt;</description>
    <pubDate>Wed, 24 May 2017 20:43:26 GMT</pubDate>
    <dc:creator>Bernardino Tellez</dc:creator>
    <dc:date>2017-05-24T20:43:26Z</dc:date>
    <item>
      <title>ISE CA Certificates</title>
      <link>https://community.cisco.com/t5/network-access-control/ise-ca-certificates/m-p/3053733#M22732</link>
      <description>&lt;P&gt;I´m using ISE 2.1 as CA for BYOD and deploying user certificates to devices. Everything works fine in the provisioning and EAP authentication.&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;Taking prrofit of the ISE CA I would like to use it for other platforms, I mean servers, proxies.... I would like to know if it is possible to sing certificates for other subordinates root CA´s or servers.&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;I also exported root CA certificates and private keys by CLI,&amp;nbsp;trying to import them to another CA server but the file is encrypted, of course I know the password, but it is a file with no format.&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;Does anyone knows if it is possible to use ISE CA as an "standard " PKI CA server?&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;Thanks.&lt;/P&gt;</description>
      <pubDate>Mon, 11 Mar 2019 07:44:29 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ise-ca-certificates/m-p/3053733#M22732</guid>
      <dc:creator>alberx</dc:creator>
      <dc:date>2019-03-11T07:44:29Z</dc:date>
    </item>
    <item>
      <title>Technically you can use ISE</title>
      <link>https://community.cisco.com/t5/network-access-control/ise-ca-certificates/m-p/3053734#M22733</link>
      <description>&lt;P&gt;Technically you can use ISE as a CA. However, this is not recommended because most likely it will not scale.&lt;/P&gt;
&lt;P&gt;What is not clear to me is why you are trying to export the root certificate and private key and import it to another CA. Can you add more details?&lt;/P&gt;
&lt;P&gt;@berna_tllz&lt;/P&gt;</description>
      <pubDate>Wed, 24 May 2017 20:43:26 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ise-ca-certificates/m-p/3053734#M22733</guid>
      <dc:creator>Bernardino Tellez</dc:creator>
      <dc:date>2017-05-24T20:43:26Z</dc:date>
    </item>
    <item>
      <title>Hi Bernardino.</title>
      <link>https://community.cisco.com/t5/network-access-control/ise-ca-certificates/m-p/3053735#M22736</link>
      <description>&lt;P&gt;Hi Bernardino.&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;I want&amp;nbsp;to use ISE root certificate ( or to sign a subordinate Root certificate) for a proxy service and intercept SSL.&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;As my client endpoints already have this root certificate installed via the BYOD provision process I would like to take profit and avoid the necessity to distribute another certificate to my clients. Much of them are private devices and I can not control them.&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;Thanks.&lt;/P&gt;</description>
      <pubDate>Thu, 25 May 2017 08:37:24 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ise-ca-certificates/m-p/3053735#M22736</guid>
      <dc:creator>alberx</dc:creator>
      <dc:date>2017-05-25T08:37:24Z</dc:date>
    </item>
    <item>
      <title>What you can do is to deploy</title>
      <link>https://community.cisco.com/t5/network-access-control/ise-ca-certificates/m-p/3053736#M22737</link>
      <description>&lt;P&gt;&lt;/P&gt;
&lt;P&gt;What you can do is to deploy a Root CA (if you don't have it yet) and make the PAN a subordinate of that CA. In that way, all the endpoint certificates will trust the Root certificate. In that scenario, you can use your Root CA to sign the proxy's certificate without trust issues from the BYOD clients. This will also help you with any other service that requires a certificate.&lt;/P&gt;
&lt;P&gt;The downside is that you will need to redeploy the BYOD certificates. You can read about this in the following link:&lt;/P&gt;
&lt;P&gt;http://www.cisco.com/c/en/us/td/docs/security/ise/2-0/admin_guide/b_ise_admin_guide_20/b_ise_admin_guide_20_chapter_0111.html#task_E458E69FA39941BBAA9799AAD7FDC644&lt;/P&gt;
&lt;P&gt;&amp;nbsp;Twitter: @berna_tllz&lt;/P&gt;</description>
      <pubDate>Thu, 25 May 2017 14:25:06 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ise-ca-certificates/m-p/3053736#M22737</guid>
      <dc:creator>Bernardino Tellez</dc:creator>
      <dc:date>2017-05-25T14:25:06Z</dc:date>
    </item>
    <item>
      <title>Yes, I already knew this.</title>
      <link>https://community.cisco.com/t5/network-access-control/ise-ca-certificates/m-p/3053737#M22741</link>
      <description>&lt;P&gt;Yes, I already knew this.&lt;/P&gt;
&lt;P&gt;But my client still does not&amp;nbsp;have PKI infrastructure and I don´t want to create it for them.&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;Thanks anyway.&lt;/P&gt;</description>
      <pubDate>Thu, 25 May 2017 14:46:16 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ise-ca-certificates/m-p/3053737#M22741</guid>
      <dc:creator>alberx</dc:creator>
      <dc:date>2017-05-25T14:46:16Z</dc:date>
    </item>
  </channel>
</rss>

