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?
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?
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.