<?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: Cisco ISE Authentication failed in Network Access Control</title>
    <link>https://community.cisco.com/t5/network-access-control/cisco-ise-authentication-failed/m-p/3837590#M473898</link>
    <description>&lt;P&gt;Not a problem.&amp;nbsp; I know that at least with some mobile devices, it will prompt the user to access the RADIUS server certificate even if the certificate has been signed by a trusted root authority in its certificate store which results in the end user having to accept the certificate before it will allow the exchange of credentials.&amp;nbsp; This is particularly true with iOS devices.&amp;nbsp; One method to counter that behavior is to use wildcard certificates on your PSNs.&amp;nbsp; That way, the end user will only have to accept the certificate once.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Regards,&lt;/P&gt;
&lt;P&gt;-Tim&lt;/P&gt;</description>
    <pubDate>Fri, 12 Apr 2019 12:54:24 GMT</pubDate>
    <dc:creator>Timothy Abbott</dc:creator>
    <dc:date>2019-04-12T12:54:24Z</dc:date>
    <item>
      <title>Cisco ISE Authentication failed</title>
      <link>https://community.cisco.com/t5/network-access-control/cisco-ise-authentication-failed/m-p/3837566#M473894</link>
      <description>&lt;P&gt;Hello everyone,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;i got a lot of authentication failed and the message is.&lt;/P&gt;&lt;TABLE border="0"&gt;&lt;TBODY&gt;&lt;TR&gt;&lt;TD&gt;Event&lt;/TD&gt;&lt;TD&gt;5440 Endpoint abandoned EAP session and started new&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD&gt;Failure Reason&lt;/TD&gt;&lt;TD&gt;5440 Endpoint abandoned EAP session and started new&lt;/TD&gt;&lt;/TR&gt;&lt;/TBODY&gt;&lt;/TABLE&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;What could be the reason?&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thank you in advance.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Michele&lt;/P&gt;</description>
      <pubDate>Fri, 12 Apr 2019 12:10:58 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/cisco-ise-authentication-failed/m-p/3837566#M473894</guid>
      <dc:creator>Michele Toblini</dc:creator>
      <dc:date>2019-04-12T12:10:58Z</dc:date>
    </item>
    <item>
      <title>Re: Cisco ISE Authentication failed</title>
      <link>https://community.cisco.com/t5/network-access-control/cisco-ise-authentication-failed/m-p/3837579#M473895</link>
      <description>&lt;P&gt;It could be the result of the supplicant on the endpoint not being correctly configured.&amp;nbsp; If you feel the supplicant is configured correctly and continue to get that error message, please open a TAC case.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Regards,&lt;/P&gt;
&lt;P&gt;-Tim&lt;/P&gt;</description>
      <pubDate>Fri, 12 Apr 2019 12:44:23 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/cisco-ise-authentication-failed/m-p/3837579#M473895</guid>
      <dc:creator>Timothy Abbott</dc:creator>
      <dc:date>2019-04-12T12:44:23Z</dc:date>
    </item>
    <item>
      <title>Re: Cisco ISE Authentication failed</title>
      <link>https://community.cisco.com/t5/network-access-control/cisco-ise-authentication-failed/m-p/3837587#M473897</link>
      <description>&lt;P&gt;we have ise 2.4 patch 6, sadly i don't have my hands on those devices, i suppose they are smartphones. If i get one i could investigate further. I just saw many logs from different users failing for this reason so i asked here.&lt;/P&gt;&lt;P&gt;Thanks for your reply.&lt;/P&gt;</description>
      <pubDate>Fri, 12 Apr 2019 12:49:26 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/cisco-ise-authentication-failed/m-p/3837587#M473897</guid>
      <dc:creator>Michele Toblini</dc:creator>
      <dc:date>2019-04-12T12:49:26Z</dc:date>
    </item>
    <item>
      <title>Re: Cisco ISE Authentication failed</title>
      <link>https://community.cisco.com/t5/network-access-control/cisco-ise-authentication-failed/m-p/3837590#M473898</link>
      <description>&lt;P&gt;Not a problem.&amp;nbsp; I know that at least with some mobile devices, it will prompt the user to access the RADIUS server certificate even if the certificate has been signed by a trusted root authority in its certificate store which results in the end user having to accept the certificate before it will allow the exchange of credentials.&amp;nbsp; This is particularly true with iOS devices.&amp;nbsp; One method to counter that behavior is to use wildcard certificates on your PSNs.&amp;nbsp; That way, the end user will only have to accept the certificate once.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Regards,&lt;/P&gt;
&lt;P&gt;-Tim&lt;/P&gt;</description>
      <pubDate>Fri, 12 Apr 2019 12:54:24 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/cisco-ise-authentication-failed/m-p/3837590#M473898</guid>
      <dc:creator>Timothy Abbott</dc:creator>
      <dc:date>2019-04-12T12:54:24Z</dc:date>
    </item>
    <item>
      <title>Re: Cisco ISE Authentication failed</title>
      <link>https://community.cisco.com/t5/network-access-control/cisco-ise-authentication-failed/m-p/3837818#M473899</link>
      <description>&lt;P&gt;Unless you are troubleshooting a particular user, you can really just ignore these entries.&amp;nbsp; If you do an install of any appreciable size involve mobile devices you will see these errors in the logs all the time.&amp;nbsp; If you try tracking these down you will be spending all your time doing that an many times the user wasn't even really trying to connect.&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Fri, 12 Apr 2019 19:45:36 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/cisco-ise-authentication-failed/m-p/3837818#M473899</guid>
      <dc:creator>paul</dc:creator>
      <dc:date>2019-04-12T19:45:36Z</dc:date>
    </item>
  </channel>
</rss>

