Other security settings

When authentication is successfully completed, a JWT token will be generated and sent to the client. This JWT token will by default use a randomly-generated secret key; the signed token will then have a three-hour lifespan.

With a randomly-generated secret key, it is important to not restart the DeployR service while task sequences are executing, since this will invalidate all existing keys. To avoid this, you can configure a specific key via advanced settings:

There is also a "Bypass local authentication" switch. This is presently required to allow communication from the StifleR service, as well as communication from PowerShell scripts run on the DeployR server that access DeployR web services.