XML requests Getting pending from Zonedirector when authenticating against radius

  • 2
  • Question
  • Updated 3 months ago
  • Answered
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

<ruckus><req-password>*********</req-password><version>1.0</version><command cmd="user-authenticate" ipaddr="192.168.1.135" macaddr="94:39:**:**:46:1f" name="discs" password="******"/></ruckus>";              
<ruckus><version>1.0</version><response-code>202</response-code><message>Authentication pending</message></ruckus>
How do i get past this or what is the Polling address to get completion.
Photo of seyton hayes

seyton hayes

  • 2 Posts
  • 0 Reply Likes
  • mildly frustrated

Posted 2 years ago

  • 2
Photo of Hoang Tung

Hoang Tung

  • 19 Posts
  • 1 Reply Like
Hi, Did you check the authentication port? Do you have VLAN?
Photo of Dmitry Ivanko

Dmitry Ivanko

  • 11 Posts
  • 0 Reply Likes
You need to send another request to check user status.  This request completes auth process. There is the XML below
<ruckus> 
<req-password>my password</req-password>
<version>1.0</version>
<command cmd="check-user-status" ipaddr="10.0.38.253" macaddr="**:**:**:**:**:**" name="**" password="************"/>
</ruckus>
This request returns an XML response with status code
(Edited)
Photo of jwalker

jwalker

  • 3 Posts
  • 1 Reply Like
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?
Photo of Dmitry Ivanko

Dmitry Ivanko

  • 11 Posts
  • 0 Reply Likes
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.
Photo of jwalker

jwalker

  • 3 Posts
  • 1 Reply Like
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.