Checkhistory job should not reuse login credential from different users

Current Situation

Wenn a user credential is used for the JobSchedulerCheckHistoryJSAdapterClass job, and the job JobSchedulerStartLatecomersJSAdapterClass must have a valid login. The login credentials may come from the private.conf configuration file or parameters. The parameter values may come from a credential store.
When user A logged in successully a valid access token is available. When now user B logs in then the access token from the user A login will be reused. Also the login from user A is reused when the password for the credential store is wrong.

Desired Behavior

When a user logs in an access token will be genereates. This access token only should be reused by this user. When another user logs in, a new access token should be created. An exception should be thrown when the password for the credential store is wrong.

How to approve

Login with user A. Then try to login with user B that have no valid credentials e.g. a wrong password. This login should be rejected.