<?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: ISW Radius over Http/https in ExtremeWireless (General)</title>
    <link>https://community.extremenetworks.com/t5/extremewireless-general/isw-radius-over-http-https/m-p/68776#M2555</link>
    <description>Hi Joe,&lt;BR /&gt;
&lt;BR /&gt;
Cisco IOS Software with the HTTP V1.1 ServerIn releases of Cisco IOS Software with the HTTP V1.1 server, the HTTP sessions do not use vtys. They use sockets.&lt;BR /&gt;
&lt;BR /&gt;
HTTP V1.1 Server - Before Cisco Bug ID CSCeb82510Before the integration of Cisco bug ID &lt;A href="https://tools.cisco.com/bugsearch/bug/CSCeb82510" target="_blank" rel="nofollow noreferrer noopener"&gt;CSCeb82510&lt;/A&gt; (&lt;A href="https://tools.cisco.com/RPF/register/register.do" target="_blank" rel="nofollow noreferrer noopener"&gt;registered&lt;/A&gt; customers only) in Cisco IOS Software Releases 12.3(7.3) and 12.3(7.3)T, the HTTP V1.1 server has to use the same authentication and authorization method that is configured for the console.&lt;BR /&gt;
&lt;BR /&gt;
&lt;BLOCKQUOTE&gt;ip http server  !  aaa new-model  aaa authentication login CONSOLEandHTTP radius local  aaa authorization exec CONSOLEandHTTP radius local  !  ip http authentication aaa  !  line con 0   login authentication CONSOLEandHTTP   authorization exec CONSOLEandHTTP&lt;/BLOCKQUOTE&gt;HTTP V1.1 Server - After Cisco Bug ID CSCeb82510With the integration of Cisco bug ID &lt;A href="https://tools.cisco.com/bugsearch/bug/CSCeb82510" target="_blank" rel="nofollow noreferrer noopener"&gt;CSCeb82510&lt;/A&gt; (&lt;A href="https://tools.cisco.com/RPF/register/register.do" target="_blank" rel="nofollow noreferrer noopener"&gt;registered&lt;/A&gt; customers only) in Cisco IOS Software Releases 12.3(7.3) and 12.3(7.3)T, the HTTP server can use independent authentication and authorization methods of its own, with new keywords in the ip http authentication aaa command. The new keywords are:&lt;BR /&gt;
&lt;BR /&gt;
&lt;BLOCKQUOTE&gt;router(config)#ip http authentication aaa command-authorization listname    router(config)#ip http authentication aaa exec-authorization listname    router(config)#ip http authentication aaa login-authentication listname    &lt;/BLOCKQUOTE&gt;This is example output:&lt;BR /&gt;
&lt;BR /&gt;
&lt;BLOCKQUOTE&gt;ip http server  !  aaa new-model  aaa authentication login HTTPonly radius local  aaa authorization exec HTTPonly radius local  !  ip http authentication aaa  ip http authentication aaa exec-authorization HTTPonly  ip http authentication aaa login-authentication HTTPonly&lt;/BLOCKQUOTE&gt;DebugIssue these debug commands in order to troubleshoot problems with HTTP authentication/authorization:&lt;BR /&gt;
&lt;BR /&gt;
&lt;BLOCKQUOTE&gt;debug ip tcp transactions  debug modem     !--- If you use the HTTP 1.0 server.    debug ip http authentication  debug aaa authentication  debug aaa authorization &lt;/BLOCKQUOTE&gt;debug radius &lt;BR /&gt;
&lt;BR /&gt;</description>
    <pubDate>Mon, 22 Oct 2018 15:25:00 GMT</pubDate>
    <dc:creator>roxanne</dc:creator>
    <dc:date>2018-10-22T15:25:00Z</dc:date>
    <item>
      <title>ISW Radius over Http/https</title>
      <link>https://community.extremenetworks.com/t5/extremewireless-general/isw-radius-over-http-https/m-p/68775#M2554</link>
      <description>Community,&lt;BR /&gt;
&lt;BR /&gt;
I configured the switch for Radius over ssh and telnet. However, when I setup the switch for to use radius over http/https I get the following error:&lt;BR /&gt;
&lt;BR /&gt;
Insufficient Privilege Level&lt;BR /&gt;
&lt;BR /&gt;
The web page is non-accessible. Please use the valid privilege level.&lt;BR /&gt;
&lt;BR /&gt;
The ssh and telnet work fine but not sure how to configure the privilege level for http/https use since my user account is already priv 15.&lt;BR /&gt;
&lt;BR /&gt;
Thanks,&lt;BR /&gt;
&lt;BR /&gt;
-Joe</description>
      <pubDate>Fri, 19 Oct 2018 01:49:00 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremewireless-general/isw-radius-over-http-https/m-p/68775#M2554</guid>
      <dc:creator>Technolust</dc:creator>
      <dc:date>2018-10-19T01:49:00Z</dc:date>
    </item>
    <item>
      <title>Re: ISW Radius over Http/https</title>
      <link>https://community.extremenetworks.com/t5/extremewireless-general/isw-radius-over-http-https/m-p/68776#M2555</link>
      <description>Hi Joe,&lt;BR /&gt;
&lt;BR /&gt;
Cisco IOS Software with the HTTP V1.1 ServerIn releases of Cisco IOS Software with the HTTP V1.1 server, the HTTP sessions do not use vtys. They use sockets.&lt;BR /&gt;
&lt;BR /&gt;
HTTP V1.1 Server - Before Cisco Bug ID CSCeb82510Before the integration of Cisco bug ID &lt;A href="https://tools.cisco.com/bugsearch/bug/CSCeb82510" target="_blank" rel="nofollow noreferrer noopener"&gt;CSCeb82510&lt;/A&gt; (&lt;A href="https://tools.cisco.com/RPF/register/register.do" target="_blank" rel="nofollow noreferrer noopener"&gt;registered&lt;/A&gt; customers only) in Cisco IOS Software Releases 12.3(7.3) and 12.3(7.3)T, the HTTP V1.1 server has to use the same authentication and authorization method that is configured for the console.&lt;BR /&gt;
&lt;BR /&gt;
&lt;BLOCKQUOTE&gt;ip http server  !  aaa new-model  aaa authentication login CONSOLEandHTTP radius local  aaa authorization exec CONSOLEandHTTP radius local  !  ip http authentication aaa  !  line con 0   login authentication CONSOLEandHTTP   authorization exec CONSOLEandHTTP&lt;/BLOCKQUOTE&gt;HTTP V1.1 Server - After Cisco Bug ID CSCeb82510With the integration of Cisco bug ID &lt;A href="https://tools.cisco.com/bugsearch/bug/CSCeb82510" target="_blank" rel="nofollow noreferrer noopener"&gt;CSCeb82510&lt;/A&gt; (&lt;A href="https://tools.cisco.com/RPF/register/register.do" target="_blank" rel="nofollow noreferrer noopener"&gt;registered&lt;/A&gt; customers only) in Cisco IOS Software Releases 12.3(7.3) and 12.3(7.3)T, the HTTP server can use independent authentication and authorization methods of its own, with new keywords in the ip http authentication aaa command. The new keywords are:&lt;BR /&gt;
&lt;BR /&gt;
&lt;BLOCKQUOTE&gt;router(config)#ip http authentication aaa command-authorization listname    router(config)#ip http authentication aaa exec-authorization listname    router(config)#ip http authentication aaa login-authentication listname    &lt;/BLOCKQUOTE&gt;This is example output:&lt;BR /&gt;
&lt;BR /&gt;
&lt;BLOCKQUOTE&gt;ip http server  !  aaa new-model  aaa authentication login HTTPonly radius local  aaa authorization exec HTTPonly radius local  !  ip http authentication aaa  ip http authentication aaa exec-authorization HTTPonly  ip http authentication aaa login-authentication HTTPonly&lt;/BLOCKQUOTE&gt;DebugIssue these debug commands in order to troubleshoot problems with HTTP authentication/authorization:&lt;BR /&gt;
&lt;BR /&gt;
&lt;BLOCKQUOTE&gt;debug ip tcp transactions  debug modem     !--- If you use the HTTP 1.0 server.    debug ip http authentication  debug aaa authentication  debug aaa authorization &lt;/BLOCKQUOTE&gt;debug radius &lt;BR /&gt;
&lt;BR /&gt;</description>
      <pubDate>Mon, 22 Oct 2018 15:25:00 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremewireless-general/isw-radius-over-http-https/m-p/68776#M2555</guid>
      <dc:creator>roxanne</dc:creator>
      <dc:date>2018-10-22T15:25:00Z</dc:date>
    </item>
    <item>
      <title>Re: ISW Radius over Http/https</title>
      <link>https://community.extremenetworks.com/t5/extremewireless-general/isw-radius-over-http-https/m-p/68777#M2556</link>
      <description>Thanks Roxanne, I'm not sure if this will fix the issue on the Extreme switch though. Unless you are referring to configuring the uplink switch for this. I do have the extreme switch connected to a CISCO 2960. &lt;BR /&gt;
&lt;BR /&gt;
-Joe&lt;BR /&gt;</description>
      <pubDate>Mon, 22 Oct 2018 18:03:00 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremewireless-general/isw-radius-over-http-https/m-p/68777#M2556</guid>
      <dc:creator>Technolust</dc:creator>
      <dc:date>2018-10-22T18:03:00Z</dc:date>
    </item>
    <item>
      <title>Re: ISW Radius over Http/https</title>
      <link>https://community.extremenetworks.com/t5/extremewireless-general/isw-radius-over-http-https/m-p/68778#M2557</link>
      <description>&lt;P&gt;Hi Joe,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I am currently trying to configure radius (using freeradius)&amp;nbsp;for some ISW switches but without success. I have been searching around and found this post. Out of curiosity;&amp;nbsp;what attribute and value did you use to get privilege level whit&amp;nbsp;ssh-login? I have tried priv-lvl = 15 but this doesn’t seem to work, and so far I have only been able to get read-access.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Best regards,&lt;/P&gt;&lt;P&gt;Hans Gudmund&lt;/P&gt;</description>
      <pubDate>Thu, 30 Jul 2020 19:13:00 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremewireless-general/isw-radius-over-http-https/m-p/68778#M2557</guid>
      <dc:creator>Hans_Gudmund_Th</dc:creator>
      <dc:date>2020-07-30T19:13:00Z</dc:date>
    </item>
    <item>
      <title>Re: ISW Radius over Http/https</title>
      <link>https://community.extremenetworks.com/t5/extremewireless-general/isw-radius-over-http-https/m-p/68779#M2558</link>
      <description>&lt;P&gt;Just an update; Radius now working&amp;nbsp;using attribute / value Cisco-AVPair=shell:priv-lvl=15.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;/Hans Gudmund&lt;/P&gt;</description>
      <pubDate>Thu, 24 Sep 2020 15:23:43 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremewireless-general/isw-radius-over-http-https/m-p/68779#M2558</guid>
      <dc:creator>Hans_Gudmund_Th</dc:creator>
      <dc:date>2020-09-24T15:23:43Z</dc:date>
    </item>
  </channel>
</rss>

