Keep the same session from one job to another?

Discussion created by Steve0 on Dec 18, 2015
Latest reply on Dec 21, 2015 by Darren_Sniezak_40
I'm using the REST web service call to login to our DynAdmin, then execute a start command

I'm able to successfully login with the REST object, but when I create another REST object to execute the start command , I get the error "Not authorized" which means that the session is not staying alive after running the first job. 

So I have a workflow of 2 REST objects. The first one logs in, then the second job will start the process. They are generating 2 seperate JSESSIONID's. I need the second job to have the same JSESSIONID so it can start once it's logged in