<?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: 12520 EAP-TLS failed SSL/TLS handshake because the client rejected the ACS local-certificate in Network Access Control</title>
    <link>https://community.cisco.com/t5/network-access-control/12520-eap-tls-failed-ssl-tls-handshake-because-the-client/m-p/3799148#M24971</link>
    <description>&lt;P&gt;Hi,&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;You need to add the CA-Certificate that signed the ISE identity certificate in the windows Certificate Store.&lt;/P&gt;
&lt;P&gt;under " Trusted Root Certificate authorities" and also intermediate CAs if the CA that signed the certificate is a sub-CA.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Mon, 11 Feb 2019 12:25:24 GMT</pubDate>
    <dc:creator>bern81</dc:creator>
    <dc:date>2019-02-11T12:25:24Z</dc:date>
    <item>
      <title>12520 EAP-TLS failed SSL/TLS handshake because the client rejected the ACS local-certificate</title>
      <link>https://community.cisco.com/t5/network-access-control/12520-eap-tls-failed-ssl-tls-handshake-because-the-client/m-p/3796871#M24969</link>
      <description>&lt;P&gt;Hi Team,&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;I am facing subjected error. this is new requirement to establish certificate based authentication wi-fi access.&lt;/P&gt;
&lt;P&gt;Kindly suggest on this.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Access Service DOTIX_WIFI&lt;/P&gt;
&lt;P&gt;Authentication Method EAP-TLS&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;11001 Received RADIUS Access-Request&lt;BR /&gt;11017 RADIUS created a new session&lt;BR /&gt;15008 Evaluating Service Selection Policy&lt;BR /&gt;15004 Matched rule&lt;BR /&gt;15012 Selected Access Service - DOTIX_WIFI&lt;BR /&gt;11507 Extracted EAP-Response/Identity&lt;BR /&gt;12500 Prepared EAP-Request proposing EAP-TLS with challenge&lt;BR /&gt;11006 Returned RADIUS Access-Challenge&lt;BR /&gt;11001 Received RADIUS Access-Request&lt;BR /&gt;11018 RADIUS is re-using an existing session&lt;BR /&gt;12502 Extracted EAP-Response containing EAP-TLS challenge-response and accepting&lt;BR /&gt;EAP-TLS as negotiated&lt;BR /&gt;12800 Extracted first TLS record; TLS handshake started.&lt;BR /&gt;12914 Empty EAP-TLS session ticket received from supplicant&lt;/P&gt;
&lt;P&gt;12911 The EAP-TLS session ticket received from supplicant while the stateless session&lt;BR /&gt;resume is disabled. Performing full authentication.&lt;BR /&gt;12805 Extracted TLS ClientHello message.&lt;BR /&gt;12806 Prepared TLS ServerHello message.&lt;BR /&gt;12807 Prepared TLS Certificate message.&lt;BR /&gt;12808 Prepared TLS ServerKeyExchange message.&lt;BR /&gt;12809 Prepared TLS CertificateRequest message.&lt;BR /&gt;12505 Prepared EAP-Request with another EAP-TLS challenge&lt;BR /&gt;11006 Returned RADIUS Access-Challenge&lt;BR /&gt;11001 Received RADIUS Access-Request&lt;BR /&gt;11018 RADIUS is re-using an existing session&lt;BR /&gt;12504 Extracted EAP-Response containing EAP-TLS challenge-response&lt;BR /&gt;12505 Prepared EAP-Request with another EAP-TLS challenge&lt;BR /&gt;11006 Returned RADIUS Access-Challenge&lt;BR /&gt;11001 Received RADIUS Access-Request&lt;BR /&gt;11018 RADIUS is re-using an existing session&lt;BR /&gt;12504 Extracted EAP-Response containing EAP-TLS challenge-response&lt;BR /&gt;12505 Prepared EAP-Request with another EAP-TLS challenge&lt;BR /&gt;11006 Returned RADIUS Access-Challenge&lt;BR /&gt;11001 Received RADIUS Access-Request&lt;BR /&gt;11018 RADIUS is re-using an existing session&lt;BR /&gt;12504 Extracted EAP-Response containing EAP-TLS challenge-response&lt;BR /&gt;12815 Extracted TLS Alert message.&lt;BR /&gt;12520 EAP-TLS failed SSL/TLS handshake because the client rejected the ACS&lt;BR /&gt;local-certificate&lt;BR /&gt;12507 EAP-TLS authentication failed&lt;BR /&gt;11504 Prepared EAP-Failure&lt;BR /&gt;11003 Returned RADIUS Access-Reject&lt;/P&gt;</description>
      <pubDate>Thu, 07 Feb 2019 15:02:44 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/12520-eap-tls-failed-ssl-tls-handshake-because-the-client/m-p/3796871#M24969</guid>
      <dc:creator>SFDCSupportNSS@cognizant.com</dc:creator>
      <dc:date>2019-02-07T15:02:44Z</dc:date>
    </item>
    <item>
      <title>Re: 12520 EAP-TLS failed SSL/TLS handshake because the client rejected the ACS local-certificate</title>
      <link>https://community.cisco.com/t5/network-access-control/12520-eap-tls-failed-ssl-tls-handshake-because-the-client/m-p/3797039#M24970</link>
      <description>&lt;P&gt;The error you are seeing is quite directed in that it actually tells you that the client is rejecting ISE during the eap set up.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;SPAN style="font-family: inherit;"&gt;Is the certificate you assigned to EAP authentication on ISE, trusted by the client? This in itself has many possible steps to check. The trust chain must be installed on the client, either by default in OS install or pushed out by admins.&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;SPAN style="font-family: inherit;"&gt;The certificate has to be valid, both who it's signed for(ise nodes) and within the valid dates.&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;One other thing I have come across is with windows native supplicants. In the connection profile, radius servers can be specified, if a radiius server not trusted in the list tries to authenticate the client, the client will reject it.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;If you're using a public CA issued cert for EAP, don't blindly assume client will trust it. Not all public CA trust chains are installed in operating systems by default.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 07 Feb 2019 17:17:43 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/12520-eap-tls-failed-ssl-tls-handshake-because-the-client/m-p/3797039#M24970</guid>
      <dc:creator>Damien Miller</dc:creator>
      <dc:date>2019-02-07T17:17:43Z</dc:date>
    </item>
    <item>
      <title>Re: 12520 EAP-TLS failed SSL/TLS handshake because the client rejected the ACS local-certificate</title>
      <link>https://community.cisco.com/t5/network-access-control/12520-eap-tls-failed-ssl-tls-handshake-because-the-client/m-p/3799148#M24971</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;You need to add the CA-Certificate that signed the ISE identity certificate in the windows Certificate Store.&lt;/P&gt;
&lt;P&gt;under " Trusted Root Certificate authorities" and also intermediate CAs if the CA that signed the certificate is a sub-CA.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 11 Feb 2019 12:25:24 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/12520-eap-tls-failed-ssl-tls-handshake-because-the-client/m-p/3799148#M24971</guid>
      <dc:creator>bern81</dc:creator>
      <dc:date>2019-02-11T12:25:24Z</dc:date>
    </item>
  </channel>
</rss>

