Token expiration settings
The tokens are generated automatically when the steps are run. The first three tokens use the built-in UC Auto Configure, UC Auto Discovery, and UC Version Import users and their permissions. The plug-in token has the permissions of the user who requests the process that plug-in runs from. These tokens are the same as those that you can create in the user interface and a command-line interface. See Tokens. Go to the UrbanCode Plug-ins website to access plug-ins that work with IBM UrbanCode Deploy and provide steps that create these tokens.
To access the Security settings area, click Settings, click System Settings, and then scroll down.
You can specify these expiration delays for tokens:
- Discovery Auth Token Expiration Delay (seconds)
- Set the expiration delay in seconds for authorization tokens that are created for autodiscovery steps. You must specify at least 300 seconds. Typically, discoveries do not require more than 300 seconds (5 minutes).
- Configure Auth Token Expiration Delay (seconds)
- Set the expiration delay in seconds for authorization tokens that are created for auto configuration steps. You must specify at least 300 seconds. Be sure to specify sufficient time for auto configuration, because the step processes stop when the token expires.
- Version Import Auth Token Expiration Delay (seconds)
- Set the expiration delay in seconds for authorization tokens that are created for version import steps. You must specify at least 300 seconds. The time required to import versions depends on component size.
- Plugin Step Auth Token Expiration Delay (seconds)
- Set the expiration delay in seconds for authorization tokens that are created for plug-in steps. You must specify at least 300 seconds. The time required to import versions depends on component size.