<?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: Authorization Issue with 802.1x in Network Access Control</title>
    <link>https://community.cisco.com/t5/network-access-control/authorization-issue-with-802-1x/m-p/4613697#M574895</link>
    <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://community.cisco.com/t5/user/viewprofilepage/user-id/1352589"&gt;@citestsco&lt;/a&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;regarding the CoA failing, it sounds as if the switch's RADIUS config is either incomplete or the shared secret in the switch's Dynamic Authorization config section is wrong. if you have two ISE PSN's, then you must enter each ISE node's IP address as a client, and also ensure that the RADIUS shared secret is the same as defined in ISE for that switch's IP address&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;PRE&gt;aaa server radius dynamic-author
 client 10.x.x.x server-key 0 RADIUS_SHARED_SECRET
 client 10.x.x.y server-key 0 RADIUS_SHARED_SECRET &lt;/PRE&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Fri, 20 May 2022 05:58:37 GMT</pubDate>
    <dc:creator>Arne Bier</dc:creator>
    <dc:date>2022-05-20T05:58:37Z</dc:date>
    <item>
      <title>Authorization Issue with 802.1x</title>
      <link>https://community.cisco.com/t5/network-access-control/authorization-issue-with-802-1x/m-p/4612247#M574838</link>
      <description>&lt;P&gt;Hi ,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Recently we have connected our switch to&amp;nbsp; a nac with dot1x .&lt;/P&gt;&lt;P&gt;We have implemented all the best practice of cisco to connect the switch to our radius server .&lt;/P&gt;&lt;P&gt;The clients authenticating successfully but as for the authorization side we are facing a problem.&lt;/P&gt;&lt;P&gt;Once the client is authenticated and authorized we cannot implement any authorization step.&lt;/P&gt;&lt;P&gt;Which means from the radius we cannot procedure an action which related to authorization such as:&lt;/P&gt;&lt;P&gt;Reauthenticate&lt;/P&gt;&lt;P&gt;Vlan assignment&lt;/P&gt;&lt;P&gt;filter-id&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Any of this does not being applied to the session of the client but the client status is "Authz success"&lt;/P&gt;&lt;P&gt;At debug we can see that the authorization details are being sent from the radius but not being applied to the switch.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Although when we perform an CoA action ( no matter which kind of CoA) we receive:&lt;/P&gt;&lt;P&gt;COA: Illegal authenticator in COA from X.X.X.X&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Please help , there is some logs from the switch while i've procedure a debug on:&lt;/P&gt;&lt;P&gt;debug aaa pod&lt;/P&gt;&lt;P&gt;debug aaa authorization&lt;/P&gt;&lt;P&gt;debug aaa coa&lt;/P&gt;&lt;P&gt;debug radius&lt;/P&gt;</description>
      <pubDate>Wed, 18 May 2022 10:31:16 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/authorization-issue-with-802-1x/m-p/4612247#M574838</guid>
      <dc:creator>citestsco</dc:creator>
      <dc:date>2022-05-18T10:31:16Z</dc:date>
    </item>
    <item>
      <title>Re: Authorization Issue with 802.1x</title>
      <link>https://community.cisco.com/t5/network-access-control/authorization-issue-with-802-1x/m-p/4612254#M574839</link>
      <description>&lt;P&gt;Hi&lt;/P&gt;
&lt;P&gt;&amp;nbsp;Which switch model and version and which radius server and version do you have?&amp;nbsp; This can be a misconfig or incompatibility.&lt;/P&gt;</description>
      <pubDate>Wed, 18 May 2022 10:41:51 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/authorization-issue-with-802-1x/m-p/4612254#M574839</guid>
      <dc:creator>Flavio Miranda</dc:creator>
      <dc:date>2022-05-18T10:41:51Z</dc:date>
    </item>
    <item>
      <title>Re: Authorization Issue with 802.1x</title>
      <link>https://community.cisco.com/t5/network-access-control/authorization-issue-with-802-1x/m-p/4612290#M574841</link>
      <description>&lt;P&gt;Can we see one port config&amp;nbsp;&lt;/P&gt;&lt;P&gt;Also you mention there is debug can we see it&lt;/P&gt;</description>
      <pubDate>Wed, 18 May 2022 11:38:27 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/authorization-issue-with-802-1x/m-p/4612290#M574841</guid>
      <dc:creator>MHM Cisco World</dc:creator>
      <dc:date>2022-05-18T11:38:27Z</dc:date>
    </item>
    <item>
      <title>Re: Authorization Issue with 802.1x</title>
      <link>https://community.cisco.com/t5/network-access-control/authorization-issue-with-802-1x/m-p/4613697#M574895</link>
      <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://community.cisco.com/t5/user/viewprofilepage/user-id/1352589"&gt;@citestsco&lt;/a&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;regarding the CoA failing, it sounds as if the switch's RADIUS config is either incomplete or the shared secret in the switch's Dynamic Authorization config section is wrong. if you have two ISE PSN's, then you must enter each ISE node's IP address as a client, and also ensure that the RADIUS shared secret is the same as defined in ISE for that switch's IP address&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;PRE&gt;aaa server radius dynamic-author
 client 10.x.x.x server-key 0 RADIUS_SHARED_SECRET
 client 10.x.x.y server-key 0 RADIUS_SHARED_SECRET &lt;/PRE&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Fri, 20 May 2022 05:58:37 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/authorization-issue-with-802-1x/m-p/4613697#M574895</guid>
      <dc:creator>Arne Bier</dc:creator>
      <dc:date>2022-05-20T05:58:37Z</dc:date>
    </item>
  </channel>
</rss>

