<?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 failed message after receiving a DUO MFA prompt in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/authorization-failed-message-after-receiving-a-duo-mfa-prompt/m-p/4898212#M1103219</link>
    <description>&lt;P&gt;Thank you Jonatan, I am able to authenticate, but now I am getting 'invalid user' when I try to access privilege mode. Any idea on why that is happening?&lt;/P&gt;</description>
    <pubDate>Thu, 03 Aug 2023 12:26:52 GMT</pubDate>
    <dc:creator>Gregory Forster</dc:creator>
    <dc:date>2023-08-03T12:26:52Z</dc:date>
    <item>
      <title>Authorization failed message after receiving a DUO MFA prompt</title>
      <link>https://community.cisco.com/t5/network-security/authorization-failed-message-after-receiving-a-duo-mfa-prompt/m-p/4897193#M1103156</link>
      <description>&lt;P&gt;Good Afternoon,&lt;/P&gt;&lt;P&gt;I have configured my Catalyst 2960L-16PS switch to use RADIUS. The RADIUS servers are the DUO AUTH-Proxies. When I try to log on to the switch I get the DUO MFA prompt to approve or decline, but as soon as I approve it gives me an "Authorization Failed" error and the putty window closes.&lt;/P&gt;&lt;P&gt;Is there something that needs to be configured on the DUO side in order for this to work?&lt;/P&gt;&lt;P&gt;I have included my switch config below.&lt;/P&gt;&lt;P&gt;no service pad&lt;BR /&gt;service tcp-keepalives-in&lt;BR /&gt;service tcp-keepalives-out&lt;BR /&gt;service timestamps debug datetime msec localtime show-timezone&lt;BR /&gt;service timestamps log datetime msec localtime show-timezone&lt;BR /&gt;service password-encryption&lt;BR /&gt;service internal&lt;BR /&gt;service sequence-numbers&lt;BR /&gt;service counters max age 10&lt;BR /&gt;!&lt;BR /&gt;hostname USNYC1-TESTSW01&lt;BR /&gt;!&lt;BR /&gt;boot-start-marker&lt;BR /&gt;boot-end-marker&lt;BR /&gt;!&lt;BR /&gt;no logging console&lt;BR /&gt;no logging monitor&lt;BR /&gt;enable secret 5 $1$oFqL$uMPm228c9FooLINHNiJkw0&lt;BR /&gt;!&lt;BR /&gt;username tptadmin privilege 15 secret 5 $1$HifD$e6CaqItzgcnp2zb2lCSR91&lt;BR /&gt;aaa new-model&lt;BR /&gt;!&lt;BR /&gt;!&lt;BR /&gt;aaa group server radius RADIUS-SERVERS-GP&lt;BR /&gt;server name AuthProxy1&lt;BR /&gt;server name AuthProxy2&lt;BR /&gt;deadtime 15&lt;BR /&gt;!&lt;BR /&gt;aaa authentication login default group RADIUS-SERVERS-GP local&lt;BR /&gt;aaa authentication login AAA-AUTHEN-LIST group RADIUS-SERVERS-GP local-case&lt;BR /&gt;aaa authentication login LOCAL-ONLY local&lt;BR /&gt;aaa authentication login CONSOLE group RADIUS-SERVERS-GP local&lt;BR /&gt;aaa authentication enable default group RADIUS-SERVERS-GP enable line&lt;BR /&gt;aaa authorization console&lt;BR /&gt;aaa authorization exec default if-authenticated&lt;BR /&gt;aaa authorization exec CONSOLE local&lt;BR /&gt;aaa authorization exec AAA-AUTHOR-LIST group RADIUS-SERVERS-GP if-authenticated&lt;BR /&gt;aaa authorization network default group RADIUS-SERVERS-GP if-authenticated&lt;BR /&gt;aaa authorization network groupauthor local&lt;BR /&gt;aaa accounting update newinfo periodic 2880&lt;BR /&gt;aaa accounting exec default start-stop group RADIUS-SERVERS-GP&lt;BR /&gt;aaa accounting exec AAA-ACCT-LIST start-stop group RADIUS-SERVERS-GP&lt;BR /&gt;aaa accounting network default start-stop group RADIUS-SERVERS-GP&lt;BR /&gt;aaa accounting connection default start-stop group RADIUS-SERVERS-GP&lt;BR /&gt;aaa accounting system default start-stop group RADIUS-SERVERS-GP&lt;BR /&gt;!&lt;BR /&gt;aaa session-id common&lt;BR /&gt;!&lt;BR /&gt;!&lt;BR /&gt;no ip domain-lookup&lt;BR /&gt;ip domain-name tpnyc.local&lt;BR /&gt;ip name-server 10.x.x.x&lt;BR /&gt;ip name-server 10.x.x.x&lt;BR /&gt;!&lt;BR /&gt;spanning-tree mode rapid-pvst&lt;BR /&gt;spanning-tree extend system-id&lt;BR /&gt;!&lt;BR /&gt;interface GigabitEthernet0/1&lt;BR /&gt;!&lt;BR /&gt;interface GigabitEthernet0/2&lt;BR /&gt;!&lt;BR /&gt;interface GigabitEthernet0/3&lt;BR /&gt;!&lt;BR /&gt;interface GigabitEthernet0/4&lt;BR /&gt;!&lt;BR /&gt;interface GigabitEthernet0/5&lt;BR /&gt;!&lt;BR /&gt;interface GigabitEthernet0/6&lt;BR /&gt;!&lt;BR /&gt;interface GigabitEthernet0/7&lt;BR /&gt;!&lt;BR /&gt;interface GigabitEthernet0/8&lt;BR /&gt;!&lt;BR /&gt;interface GigabitEthernet0/9&lt;BR /&gt;!&lt;BR /&gt;interface GigabitEthernet0/10&lt;BR /&gt;!&lt;BR /&gt;interface GigabitEthernet0/11&lt;BR /&gt;!&lt;BR /&gt;interface GigabitEthernet0/12&lt;BR /&gt;!&lt;BR /&gt;interface GigabitEthernet0/13&lt;BR /&gt;!&lt;BR /&gt;interface GigabitEthernet0/14&lt;BR /&gt;!&lt;BR /&gt;interface GigabitEthernet0/15&lt;BR /&gt;!&lt;BR /&gt;interface GigabitEthernet0/16&lt;BR /&gt;description 'Uplink to Network'&lt;BR /&gt;switchport access vlan 102&lt;BR /&gt;switchport mode access&lt;BR /&gt;spanning-tree bpdufilter enable&lt;BR /&gt;!&lt;BR /&gt;interface GigabitEthernet0/17&lt;BR /&gt;!&lt;BR /&gt;interface GigabitEthernet0/18&lt;BR /&gt;!&lt;BR /&gt;interface Vlan1&lt;BR /&gt;description 'DO NOT USE'&lt;BR /&gt;no ip address&lt;BR /&gt;no ip redirects&lt;BR /&gt;no ip unreachables&lt;BR /&gt;no ip proxy-arp&lt;BR /&gt;shutdown&lt;BR /&gt;!&lt;BR /&gt;interface Vlan102&lt;BR /&gt;description 'Site-Mgmt'&lt;BR /&gt;ip address 10.x.x.x x.x.x.x&lt;BR /&gt;no ip redirects&lt;BR /&gt;no ip unreachables&lt;BR /&gt;no ip proxy-arp&lt;BR /&gt;!&lt;BR /&gt;ip default-gateway 10.x.x.x&lt;BR /&gt;ip http server&lt;BR /&gt;ip http secure-server&lt;BR /&gt;!&lt;BR /&gt;ip radius source-interface Vlan102&lt;BR /&gt;!&lt;BR /&gt;!&lt;BR /&gt;!&lt;BR /&gt;!&lt;BR /&gt;radius server AuthProxy1&lt;BR /&gt;address ipv4 10.x.x.x auth-port 1812 acct-port 1813&lt;BR /&gt;timeout 4&lt;BR /&gt;retransmit 1&lt;BR /&gt;automate-tester username radiustest ignore-acct-port&lt;BR /&gt;key 7 11330A15403D02025730000F1D1B65283B354F370C46&lt;BR /&gt;!&lt;BR /&gt;radius server AuthProxy2&lt;BR /&gt;address ipv4 10.x.x.xauth-port 1812 acct-port 1813&lt;BR /&gt;timeout 4&lt;BR /&gt;retransmit 1&lt;BR /&gt;automate-tester username radiustest ignore-acct-port&lt;BR /&gt;key 7 012915140C240F01725665222C2D4718233E5D1E2634&lt;BR /&gt;!&lt;BR /&gt;!&lt;BR /&gt;line con 0&lt;BR /&gt;logging synchronous&lt;BR /&gt;login authentication LOCAL-ONLY&lt;BR /&gt;line vty 0 4&lt;BR /&gt;authorization exec CONSOLE&lt;BR /&gt;accounting exec AAA-ACCT-LIST&lt;BR /&gt;logging synchronous&lt;BR /&gt;login authentication AAA-AUTHEN-LIST&lt;BR /&gt;transport input ssh&lt;BR /&gt;line vty 5 15&lt;BR /&gt;authorization exec CONSOLE&lt;BR /&gt;accounting exec AAA-ACCT-LIST&lt;BR /&gt;logging synchronous&lt;BR /&gt;login authentication AAA-AUTHEN-LIST&lt;BR /&gt;transport input ssh&lt;BR /&gt;!&lt;BR /&gt;ntp logging&lt;BR /&gt;ntp authenticate&lt;BR /&gt;ntp source Vlan102&lt;BR /&gt;ntp server 10.32.51.50 prefer&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 01 Aug 2023 19:21:33 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/authorization-failed-message-after-receiving-a-duo-mfa-prompt/m-p/4897193#M1103156</guid>
      <dc:creator>Gregory Forster</dc:creator>
      <dc:date>2023-08-01T19:21:33Z</dc:date>
    </item>
    <item>
      <title>Re: Authorization failed message after receiving a DUO MFA prompt</title>
      <link>https://community.cisco.com/t5/network-security/authorization-failed-message-after-receiving-a-duo-mfa-prompt/m-p/4897257#M1103162</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;
&lt;P&gt;I'm guessing the issue is the following, assuming you're logging in via SSH.&lt;/P&gt;
&lt;P&gt;Your vty config has:&lt;BR /&gt;authorization exec CONSOLE&lt;/P&gt;
&lt;P&gt;And your aaa config has:&lt;BR /&gt;aaa authorization exec CONSOLE local&lt;/P&gt;
&lt;P&gt;So once the authentication (via duo) is done, the switch tries to verify the access authorization to users configured locally on the switch.&lt;/P&gt;
&lt;P&gt;So if you're using usernames that do not exist on the switch, you will fail the authorization.&lt;/P&gt;
&lt;P&gt;You could either change the authorization CONSOLE to if-authenticated or depending on your authentication backend to authorize via RADIUS.&lt;/P&gt;</description>
      <pubDate>Tue, 01 Aug 2023 22:25:14 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/authorization-failed-message-after-receiving-a-duo-mfa-prompt/m-p/4897257#M1103162</guid>
      <dc:creator>Jonatan Jonasson</dc:creator>
      <dc:date>2023-08-01T22:25:14Z</dc:date>
    </item>
    <item>
      <title>Re: Authorization failed message after receiving a DUO MFA prompt</title>
      <link>https://community.cisco.com/t5/network-security/authorization-failed-message-after-receiving-a-duo-mfa-prompt/m-p/4897258#M1103163</link>
      <description>&lt;P&gt;Jonatan,&lt;/P&gt;&lt;P&gt;Thank you. I did not think of that. I will give that a try and let you know the results.&lt;/P&gt;</description>
      <pubDate>Tue, 01 Aug 2023 22:33:53 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/authorization-failed-message-after-receiving-a-duo-mfa-prompt/m-p/4897258#M1103163</guid>
      <dc:creator>Gregory Forster</dc:creator>
      <dc:date>2023-08-01T22:33:53Z</dc:date>
    </item>
    <item>
      <title>Re: Authorization failed message after receiving a DUO MFA prompt</title>
      <link>https://community.cisco.com/t5/network-security/authorization-failed-message-after-receiving-a-duo-mfa-prompt/m-p/4898212#M1103219</link>
      <description>&lt;P&gt;Thank you Jonatan, I am able to authenticate, but now I am getting 'invalid user' when I try to access privilege mode. Any idea on why that is happening?&lt;/P&gt;</description>
      <pubDate>Thu, 03 Aug 2023 12:26:52 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/authorization-failed-message-after-receiving-a-duo-mfa-prompt/m-p/4898212#M1103219</guid>
      <dc:creator>Gregory Forster</dc:creator>
      <dc:date>2023-08-03T12:26:52Z</dc:date>
    </item>
    <item>
      <title>Re: Authorization failed message after receiving a DUO MFA prompt</title>
      <link>https://community.cisco.com/t5/network-security/authorization-failed-message-after-receiving-a-duo-mfa-prompt/m-p/4898224#M1103220</link>
      <description>&lt;P&gt;Ok so I added privilege level 15 to line vty 0 4 and that worked, but I do not this this is the proper way to set this up using best practices.&lt;/P&gt;</description>
      <pubDate>Thu, 03 Aug 2023 12:58:26 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/authorization-failed-message-after-receiving-a-duo-mfa-prompt/m-p/4898224#M1103220</guid>
      <dc:creator>Gregory Forster</dc:creator>
      <dc:date>2023-08-03T12:58:26Z</dc:date>
    </item>
    <item>
      <title>Re: Authorization failed message after receiving a DUO MFA prompt</title>
      <link>https://community.cisco.com/t5/network-security/authorization-failed-message-after-receiving-a-duo-mfa-prompt/m-p/4898256#M1103223</link>
      <description>&lt;P&gt;Also I discovered that none of the local accounts that are set up on the switch can log in. I get 'Invalid User' when I try to access the switch via console cable and a local user account.&lt;/P&gt;</description>
      <pubDate>Thu, 03 Aug 2023 13:58:38 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/authorization-failed-message-after-receiving-a-duo-mfa-prompt/m-p/4898256#M1103223</guid>
      <dc:creator>Gregory Forster</dc:creator>
      <dc:date>2023-08-03T13:58:38Z</dc:date>
    </item>
    <item>
      <title>Re: Authorization failed message after receiving a DUO MFA prompt</title>
      <link>https://community.cisco.com/t5/network-security/authorization-failed-message-after-receiving-a-duo-mfa-prompt/m-p/4898292#M1103224</link>
      <description>&lt;P&gt;Jonatan,&lt;/P&gt;&lt;P&gt;Disregard my question here. It is self explanatory. I would not be able to login locally so long as the Radius servers are available.&lt;/P&gt;</description>
      <pubDate>Thu, 03 Aug 2023 15:24:40 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/authorization-failed-message-after-receiving-a-duo-mfa-prompt/m-p/4898292#M1103224</guid>
      <dc:creator>Gregory Forster</dc:creator>
      <dc:date>2023-08-03T15:24:40Z</dc:date>
    </item>
  </channel>
</rss>

