25 docs tagged with "security"

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 explains how to configure secure communication between Deploy master, workers, and satellite servers using TLS/SSL technology.

This topic addresses how to resolve SSL handshake issues with Deploy when using a self-signed certificate by configuring a dedicated truststore for the command-line interface (CLI).

This topic provides a step-by-step procedure for connecting Deploy to your LDAP or Active Directory infrastructure.

This topic provides a step-by-step guide on connecting Deploy to your Atlassian Crowd instance.

This topic provides information about the Deploy concepts for using Deploy.

This topic describes how to configure Deploy to work with the log analysis tool.

This topic provides information about the logs in Deploy.

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".

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".

This topic describes how to change the encryption key password and the admin user's password in Deploy.

This topic explores how to integrate Pendo Analytics and Guidance with Deploy.

This topic describes the Permission service in Digital.ai Deploy.

This topic explains the roles and permissions in Deploy.

This topic describes how password properties and encrypted dictionary entries combine to secure sensitive data in Deploy.

What are the implications of deprecating TLS protocol versions 1.0 and 1.1?

Stitch sources are created under the Configuration tab of the CI Explorer. Using configuration or folder permissions, you can show/hide Stitch sources. As a Stitch source is also a CI, it has the same logic for permissions as all other CI’s.

This topic describes how to set up and configure LDAP with Deploy.

This topic provides Deploy provides information about fine-grained security settings based on roles and permissions that you can configure in the GUI and through the command-line interface (CLI).

This topic describes the default permission settings in Deploy after installation. Initially, no permissions are granted to any user, except for administrator users, who have all permissions.

This topic describes how to define one or more sets of credentials in the Configuration section of the CI Library for use with source artifacts. Admin global permissions are required to define these credentials. Once defined, you can use them to provide a username and password for any HTTP URL that requires authentication.

This topic describes how Digital.ai Deploy provides a mechanism to automatically encrypt passwords, allowing you to reference them without storing third-party passwords in plain text in configuration files.

This article describes how to define one or more sets of proxy servers to be used with source artifacts in the Configuration section of the CI Library.

This topic describes how to manage credentials for multiple remote hosts that share the same authentication details. To simplify credential management, you can configure a single CI to define shared credentials for any remote host requiring authentication. When defining an overthere host connection, you can then select the shared credentials CI.

This topic provides information on how to update the digital certificate.