<?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 Cisco ACS 4.2 SSL certificate 2048bit in Network Access Control</title>
    <link>https://community.cisco.com/t5/network-access-control/cisco-acs-4-2-ssl-certificate-2048bit/m-p/2251274#M111538</link>
    <description>&lt;P&gt;Greetings&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;We currently have Cisco ACS 4.2 running with verisign trusted SSL certificate running 1024bit.&amp;nbsp; This SSL certificate is used for PEAP and wireless users with WLC.&amp;nbsp; Since the new standard by Verisign is issuing 2048bit we can no longer renew 1024bit cerfificates.&amp;nbsp; Wondering if there is supportability for 2048bit or is there a requirement to upgrade?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Reading through various articles the existing Cisco ACS 4.2 has issues with anything above 1024bit&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P style="margin-left: 36pt;"&gt;&lt;STRONG&gt;Note: While Cisco Secure ACS can generate key sizes greater than 1024, the use of a key larger than 1024 does not work with PEAP. Authentication might appear to pass in Cisco Secure ACS, but the client hangs while authentication is attempted.&lt;/STRONG&gt;&lt;/P&gt;</description>
    <pubDate>Mon, 11 Mar 2019 03:37:58 GMT</pubDate>
    <dc:creator>Tuyen Nguyen</dc:creator>
    <dc:date>2019-03-11T03:37:58Z</dc:date>
    <item>
      <title>Cisco ACS 4.2 SSL certificate 2048bit</title>
      <link>https://community.cisco.com/t5/network-access-control/cisco-acs-4-2-ssl-certificate-2048bit/m-p/2251274#M111538</link>
      <description>&lt;P&gt;Greetings&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;We currently have Cisco ACS 4.2 running with verisign trusted SSL certificate running 1024bit.&amp;nbsp; This SSL certificate is used for PEAP and wireless users with WLC.&amp;nbsp; Since the new standard by Verisign is issuing 2048bit we can no longer renew 1024bit cerfificates.&amp;nbsp; Wondering if there is supportability for 2048bit or is there a requirement to upgrade?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Reading through various articles the existing Cisco ACS 4.2 has issues with anything above 1024bit&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P style="margin-left: 36pt;"&gt;&lt;STRONG&gt;Note: While Cisco Secure ACS can generate key sizes greater than 1024, the use of a key larger than 1024 does not work with PEAP. Authentication might appear to pass in Cisco Secure ACS, but the client hangs while authentication is attempted.&lt;/STRONG&gt;&lt;/P&gt;</description>
      <pubDate>Mon, 11 Mar 2019 03:37:58 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/cisco-acs-4-2-ssl-certificate-2048bit/m-p/2251274#M111538</guid>
      <dc:creator>Tuyen Nguyen</dc:creator>
      <dc:date>2019-03-11T03:37:58Z</dc:date>
    </item>
    <item>
      <title>Cisco ACS 4.2 SSL certificate 2048bit</title>
      <link>https://community.cisco.com/t5/network-access-control/cisco-acs-4-2-ssl-certificate-2048bit/m-p/2251275#M111575</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Yes, I'm aware of this document. However, it does work. I've seen PEAP with 2048bit certs working fine.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;~BR &lt;BR /&gt;Jatin Katyal &lt;BR /&gt; &lt;BR /&gt;**Do rate helpful posts**&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 09 Jul 2013 18:33:04 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/cisco-acs-4-2-ssl-certificate-2048bit/m-p/2251275#M111575</guid>
      <dc:creator>Jatin Katyal</dc:creator>
      <dc:date>2013-07-09T18:33:04Z</dc:date>
    </item>
    <item>
      <title>Cisco ACS 4.2 SSL certificate 2048bit</title>
      <link>https://community.cisco.com/t5/network-access-control/cisco-acs-4-2-ssl-certificate-2048bit/m-p/2251276#M111635</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Tuyeh,&lt;/P&gt;&lt;P&gt;Greetings.&lt;/P&gt;&lt;P&gt;Jatin says from practical experience it work. However, I wonder if that scenario will be supported by TAC (even if it works).&lt;/P&gt;&lt;P&gt;To be on the safe side, it is better to open a TAC case with Cisco asking them if that scenario is supported. If it is not and any issue happened later the TAC will not help you because you are running un-supported scenario.&lt;/P&gt;&lt;P&gt;It is also advisable to move to a newer version of ACS (5.x) as the 4.x version is going to be out of support next year (April 2014 if I remember correctly).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;HTH&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Amjad&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="color: blue;"&gt;Rating useful replies is more useful than saying &lt;SPAN style="color: green;"&gt; "&lt;SPAN style="text-decoration: underline;"&gt;Thank you&lt;/SPAN&gt;"&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 11 Jul 2013 07:23:34 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/cisco-acs-4-2-ssl-certificate-2048bit/m-p/2251276#M111635</guid>
      <dc:creator>Amjad Abdullah</dc:creator>
      <dc:date>2013-07-11T07:23:34Z</dc:date>
    </item>
  </channel>
</rss>

