Master supports token based authentication for Agent

Handling of access tokens by Master

• JobScheduler Agents can be configured to require an access token as specified by JS-1589.
• The JobScheduler Master stores the access token with the process class that specifies the Agent instance
  • for a single Agent like this:

    <process_class  remote_scheduler="http://localhost:4445" access_token="34ed218a-df88-4cc8-b90b-628d29ba58e5"/>
    

  • for Agent clusters like this:

    <process_class>
        <remote_schedulers >
            <remote_scheduler  remote_scheduler="http://Andreas-MacBook-Pro.local:4445" access_token="2bb475f2-3b1a-4207-b438-fa5f81cc5df2"/>
            <remote_scheduler  remote_scheduler="http://localhost:4445" access_token="34ed218a-df88-4cc8-b90b-628d29ba58e5"/>
        </remote_schedulers>
    </process_class>
    

• The Master forwards the access token with each HTTP request to the respective Agent.