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.
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.
This topic describes how to configure Release to use an Atlassian Crowd to authenticate users and retrieve role (group) membership. In Release, Atlassian Crowd users and groups become principals that you can assign to roles. Global permissions are assigned at the role level.
This topic describes how to configure Keycloak to authenticate Release users and REST API calls (using the Bearer Token Authorization).
This topic explains how to configure task access Release, allowing you to manage who can view or execute specific tasks within a release.
This topic outlines how to configure session timeout and session storage settings in Release.
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.
This topic describes how to configure Release to use an LDAP repository to authenticate users and retrieve role, group, membership.
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".
This topic explains how to change the encryption key password and the admin user's password in Release.
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.
Pendo.io is a Product Analytics platform used in Release to enrich the product experience and provide insights to the product management team.
This topic describes how to create and use Personal Access Tokens (PAT).
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.
This topics provides information about creating and configuring a truststore, importing certificates, and adjusting Release settings to ensure secure communication with the Deploy server.
The Release Setup Wizard can generate a self-signed digital certificate for secure communications.
This topic explains user management in Digital.ai Release, including how users are identified and authenticated through valid credentials.