<?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: ACS - reject reason in Network Access Control</title>
    <link>https://community.cisco.com/t5/network-access-control/acs-reject-reason/m-p/1280416#M393727</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;..but if it is a customer request....&lt;/P&gt;&lt;P&gt;an application, when authenticating users, should differentiate between users that are disabled and those that mistyped user/pass&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Thu, 23 Jul 2009 12:00:09 GMT</pubDate>
    <dc:creator>kpanduric</dc:creator>
    <dc:date>2009-07-23T12:00:09Z</dc:date>
    <item>
      <title>ACS - reject reason</title>
      <link>https://community.cisco.com/t5/network-access-control/acs-reject-reason/m-p/1280413#M393720</link>
      <description>&lt;P&gt;Is it possible to configure ACS 4.x to return reason that caused the user to be rejected (e.g. account disabled, wrong user/password...) to NAS?&lt;/P&gt;</description>
      <pubDate>Sun, 10 Mar 2019 23:36:12 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/acs-reject-reason/m-p/1280413#M393720</guid>
      <dc:creator>kpanduric</dc:creator>
      <dc:date>2019-03-10T23:36:12Z</dc:date>
    </item>
    <item>
      <title>Re: ACS - reject reason</title>
      <link>https://community.cisco.com/t5/network-access-control/acs-reject-reason/m-p/1280414#M393722</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;The communication between the AAA client and the NAS is done using Radius:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;1 Access-Request&lt;/P&gt;&lt;P&gt;2 Access-Accept&lt;/P&gt;&lt;P&gt;3 Access-Reject&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;An External Database like Active Directory would send those type of messages (account disabled, wrong user/password..) to the AAA Server, but I don't beleive it can forward them to the AAA client.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks...&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 22 Jul 2009 14:35:31 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/acs-reject-reason/m-p/1280414#M393722</guid>
      <dc:creator>ansalaza</dc:creator>
      <dc:date>2009-07-22T14:35:31Z</dc:date>
    </item>
    <item>
      <title>Re: ACS - reject reason</title>
      <link>https://community.cisco.com/t5/network-access-control/acs-reject-reason/m-p/1280415#M393724</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;...and there is a good reason why you *never* do this.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Security 101 - dont tell users why an authentication has failed - they might not be who you think they are.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Yes its a pain when real valid users cant authenticate and they have to ring the support team. But the alternative is far worse.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 23 Jul 2009 10:01:52 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/acs-reject-reason/m-p/1280415#M393724</guid>
      <dc:creator>darpotter</dc:creator>
      <dc:date>2009-07-23T10:01:52Z</dc:date>
    </item>
    <item>
      <title>Re: ACS - reject reason</title>
      <link>https://community.cisco.com/t5/network-access-control/acs-reject-reason/m-p/1280416#M393727</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;..but if it is a customer request....&lt;/P&gt;&lt;P&gt;an application, when authenticating users, should differentiate between users that are disabled and those that mistyped user/pass&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 23 Jul 2009 12:00:09 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/acs-reject-reason/m-p/1280416#M393727</guid>
      <dc:creator>kpanduric</dc:creator>
      <dc:date>2009-07-23T12:00:09Z</dc:date>
    </item>
    <item>
      <title>Re: ACS - reject reason</title>
      <link>https://community.cisco.com/t5/network-access-control/acs-reject-reason/m-p/1280417#M393729</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;No, never.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If you do, then you're telling a potential hacker that the username he/she just tried is valid.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Getting a username is half the job done.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Remember ACS is aimed at remote access and wireless where logins could be coming from anywhere.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;What it could do is include a failure message to the end user that includes the help desk telephone number and perhaps a unique incident id. Thats secure and helpful.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 23 Jul 2009 12:43:11 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/acs-reject-reason/m-p/1280417#M393729</guid>
      <dc:creator>darpotter</dc:creator>
      <dc:date>2009-07-23T12:43:11Z</dc:date>
    </item>
  </channel>
</rss>

