Caching Run-As User Credentials

You can set a property for the 3DOrchestrate Distribution Server to control the life cycle and expiration of run-as user credentials.

Using this property to cache user credentials only applies under the following conditions:

  • When run-as security is enabled on the 3DOrchestrate Distribution Server (in the fiper.security.runas.enabled property).
  • When 3DPassport is integrated with LDAP or another external authentication system and the run-as OS usernames and 3DPassport usernames are the same.

See Also
SMAExeServer.properties File

Edit the <server_install_dir>/config/SMAExeServer-xxxx.properties file in the 3DOrchestrate Distribution Server installation to set the following property: 

fiper.system.credentials.expiry=<expiration>

You can set <expiration> to the following values:

JOB
The operating system run-as credentials (username and password) are tied to each specific job and will expire when the job execution completes in 3DOrchestrate. This setting is the default behavior, in which credentials are not cached.
<#days>

The number of days that the run-as credentials should be cached in 3DOrchestrate. Set this value in the format "#-DAYS", for example: 1-DAYS or 5-DAYS.

You can also specify the time in minutes, for example: 15-MIN.

While the run-as credentials are cached in 3DOrchestrate, they can be re-used implicitly in a client app to execute any simulation process (job). The end-user can simply click Run in the client app without re-entering the username and password.