In Release 8.5 and later, you can use custom dashboards to build a security and compliance dashboard to ensure that your applications meet the compliance requirements and to help you identify applications that are failing to meet security standards. For more information about custom dashboards, see Configure custom dashboards.
Multiple blueprints can be composed into one master blueprint which specifies the deployment model for multiple included blueprints, by using includeBefore and includeAfter parameters. This allows you to scale your deployment and release models with any number of blueprints. During the implementation of a composed blueprint, the CLI will work through the blueprints in the sequence defined, merging the questions into a single list and applying any custom values that were defined in the composed blueprint. For more information on the YAML fields that enable composable blueprints, see IncludeBefore/IncludeAfter fields for composability.
Release has a role-based security system with two types of users:
This topic describes how to configure Keycloak to authenticate Release users and REST API calls (using the Bearer Token Authorization).
What are Tasks?
Release timeout
In Release you can configure the file upload properties. File upload properties are used to set a limit for the size of uploaded files and to restrict content accepted by Release.
This topic describes how support Single Sign-On (SSO) by configuring Release to use Integrated Windows Authentication to authenticate users and retrieve role (group) membership without prompting the users for a user name and password. In Release, Active Directory users and groups become principals that you can assign to roles.
Digital.ai Release has a role-based security system with two types of users:
By default, the Digital.ai Release server writes information, such as: warnings, errors, and log messages to your terminal output and to XLRELEASESERVER_HOME/log/xl-release.log.
You can specify and maintain global permissions, roles, and users for Deploy in YAML, enabling you to manage this aspect of your Deploy configuration "as code".
Change the encryption key password
You can specify and maintain global permissions, roles, and users for Release in YAML, enabling you to manage this aspect of your Release configuration "as code".
Release provides a mechanism to automatically encrypt passwords and enables you to refer to them, so you do not need to store third-party passwords in plain text in configuration files. To declare a new third-party password:
Pendo.io is a Product Analytics platform used in Release to enrich the product experience and provide insights to the product management team.
Personal Access Tokens (PAT) are used as an alternative to passwords for authenticating with Digital.ai Release. You can use PATs with public APIs and webhook endpoints.
What are the implications of deprecating TLS protocol versions 1.0 and 1.1?
* This topic describes how to configure Release authentication using the OpenID Connect (OIDC) protocol. OpenID Connect (OIDC) is an identity layer built on top of the OAuth 2.0 protocol and supported by various OAuth 2.0 providers.
If you configured your Deploy server to use a self-signed certificate and then added the server to Release, you will notice that testing the connection fails with the following error:
The Release Setup Wizard can generate a self-signed digital certificate for secure communications. This can cause issues in situations where Release needs to be accessed via a URL other than https5516, because the common name in the certificate is localhost. For more information, see Install Release using a manual setup.
Who are users?