topic XML requests Getting pending from Zonedirector when authenticating against radius in ZoneDirector

XML requests Getting pending from Zonedirector when authenticating against radius

seyton_hayes — Wed, 11 Mar 2015 14:15:17 GMT

Why when i use /admin/_portalintf.jsp xml request Authorization to any radius server i get a xml 202 Authentication pending but if i use local database i get Successful i have tried with multiple radius servers any help would be appreciated

*********1.0";

1.0202Authentication pending

How do i get past this or what is the Polling address to get completion.

Re: XML requests Getting pending from Zonedirector when authenticating against radius

hoang_tung_7073 — Fri, 13 Mar 2015 00:59:08 GMT

Hi, Did you check the authentication port? Do you have VLAN?

Re: XML requests Getting pending from Zonedirector when authenticating against radius

dmitry_ivanko — Tue, 22 Sep 2015 09:40:15 GMT

You need to send another request to check user status. This request completes auth process. There is the XML below

 
my password
1.0

This request returns an XML response with status code

Re: XML requests Getting pending from Zonedirector when authenticating against radius

jason_walker_8w — Wed, 26 Apr 2017 13:03:34 GMT

Dmitry,
I tried your suggestion, as I was experiencing the same problem as Seyton. However after making the request "check-user-status" I get back (305) Command Parameter not supported.

Did anyone get a solution for this issue?

Re: XML requests Getting pending from Zonedirector when authenticating against radius

dmitry_ivanko — Wed, 03 May 2017 11:55:26 GMT

hi jwalker,

I can't help to you, I don't work with ZoneDirector API since 9.6 release. I have not found the fresh Northbound API documentation at the https://support.ruckuswireless.com. Old software release works with next flow

link

I think you need to ask Ruckus support about the new documentation.

Re: XML requests Getting pending from Zonedirector when authenticating against radius

jason_walker_8w — Wed, 03 May 2017 12:39:57 GMT

Thanks, we solved it. Turns out that we are not using DPSK, and it was still in the code base that we were using. Removed the code and all is working. The check-user-status helped out, funny it wasn't in the documentation.