Details
-
Feature
-
Status: Released (View Workflow)
-
Minor
-
Resolution: Fixed
-
1.12
-
None
Description
Current Situation
There is a job chain createApiAccessToken in the folder live/sos/rest
The job chain creates an access token and is used by the jobs JobSchedulerCheckHistoryJSAdapterClass and JobSchedulerStartLatecomers and by the pre processing monitor com.sos.jitl.restclient.CreateApiAccessToken.
Desired Behavior
Instead of creating an order for the job chain createApiAccessToken the jobs and monitors should implement the creation of acces tokens directly without creating an order. The folder live/sos/rest should be removed.
Testcase
- remove folder live/sos/rest
- restart JobScheduler
- Test Job JobSchedulerCheckHistoryJSAdapterClass
- Run the job two times. In the log for the second run it should be seen that the access token should be reused.
- Wait for the configured job session time (see JOC Manage Accounts/Main Section)
- Run the job again.
- Check in the log that a new access token have been created.
- restart JobScheduler
- Test Job JobSchedulerStartLatecomers
- Run the job two times. In the log for the second run it should be seen that the access token should be reused.
- restart JobScheduler
- Test the pre processing monitor com.sos.jitl.restclient.CreateApiAccessToken.
- Run the job that have assigned this monitor two times. In the log for the second run it should be seen that the access token should be reused.
The actual access token can be checked with this job
<job stop_on_error="no" name="job1"> <script language="java:javascript"> <![CDATA[ function spooler_process(){ spooler_log.info(spooler.variables.value("X-Access-Token")); spooler_log.info(spooler.variables.value("joc_url")); return false; } ]]> </script> <run_time /> </job>
Attachments
Issue Links
- mentioned in
-
Page Loading...