Virtual SmartZone API : How should serviceTicket be used?

  • 3
  • Question
  • Updated 3 months ago
  • Acknowledged
  • (Edited)
I'm currently building a service to communicate with a Virtual SmartZone. On startup, the service calls the v7_0/serviceTicket route and receives a service ticket back, which is used as a URI parameter for all other requests: http://docs.ruckuswireless.com/smartz...

 However, the docs do not state how long this service ticket is active for, and how old service tickets should be cleaned up. I have tried the DELETE method for this route and it appears to not work. After running DELETE on /serviceTicket with the ticket id, I still am able to use that ticket id. There is also no way to get a list of old service tickets so that they could be cleaned up.

 I am worried about creating too many service tickets, and eventually slowing down or crashing the server. Is this is a valid concern? Should I just create one serviceTicket and then use that as a constant value instead of creating a new one each time? 
Photo of Nick Knoebber

Nick Knoebber

  • 2 Posts
  • 0 Reply Likes
  • confused

Posted 9 months ago

  • 3
Photo of Michael Brado

Michael Brado, Official Rep

  • 2870 Posts
  • 399 Reply Likes
I don't know anyone with experience using "v7_0/serviceTicket" application/tool that you are asking about.
This doesn't seem to be related to the SmartZone controller.
Does the company that supports "v7_0/serviceTicket" provide answer in their docs, or have contact you can ask?
Photo of Borja Otura Garcia

Borja Otura Garcia

  • 1 Post
  • 0 Reply Likes
Hi Nick,


Same issue here. Not sure how this works.

Michael, "v7_0/serviceTicket" refers to the route required to create a serviceTicket through the Ruckus SmartZone controller API as per the documentation. link below:

http://docs.ruckuswireless.com/smartzone/5.0/vszh-public-api-reference-guide-5-0.html

BR,
Borja
 

Photo of Matt Skalecki

Matt Skalecki

  • 1 Post
  • 0 Reply Likes
Does anyone have any information on this?

On 5.1.0.0.496 I receive an 500 (internal error) response when calling the DELETE method on the serviceTicket endpoint, and the serviceTicket continues to work for other requests.

The URI of my request is 'https://{ruckuscontrollerfqdn}:8443/wsg/api/public/v8_0/serviceTicket?serviceTicket={myserviceTicket}'

The same error occurs if I use v7_0
Photo of Nick Knoebber

Nick Knoebber

  • 2 Posts
  • 0 Reply Likes
I opened a ticket up for this months ago and still haven't gotten an answer on how service ticket should be used. I ended up going the route of creating a new service ticket for every request. The DELETE method doesn't appear to work.

I still would appreciate an answer from the software developers at Ruckus on how they designed service ticket.
(Edited)
Photo of Nick Zourdos

Nick Zourdos

  • 23 Posts
  • 4 Reply Likes
Bumping this. The API documentation says that we should use serviceTicket for GET requests, but I cannot get it to work. I am able to obtain a serviceTicket value in a POST, but I keep getting "current session has timed out: error 201, no active session" when I try to make a GET. 

Can someone from Ruckus chime in with some info on whether this works or not?
Photo of Nick Zourdos

Nick Zourdos

  • 23 Posts
  • 4 Reply Likes
I rebooted my vSZ, ran a POST with {serviceTicket} in the headers, and then ran a GET with {serviceTicket} in the headers, and it worked. I ran a DEL with {serviceTicket} in the headers to kill the session, then tried the whole process over. It did not work. I have no idea how I got it working the first time. 
(Edited)