Supported only from 16.1 and above.
vManager can execute jobs in one of two modes:
Same user permissions (the account permission where the vManager server is installed) for all jobs launched by the vAPI/Jenkins.
Use the Linux account permissions of the actual user who is doing the launch operation.
Default (unchecked above) is for the vManager to launch job by using the account permissions where the server is installed.
When this box is checked, user can choose between using the same credentials used within the authentication section above, or supply a file with user/password in plain text containing only two lines:
username
password
For this (dynamic user/password), a pre-job should place any file into its working directory, and supply the full path to it.
In case this field is empty, The file name need to be: ${BUILD_NUMBER}.${BUILD_ID}.credential.input, and should be place in the working directory of the current running build.
Please fill this field only in case you want to hard code the input file name, to be consist across all builds.