Skip to main content

26 docs tagged with "security"

View all tags

Composable blueprints

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.

Deploy concepts

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

Manage Deploy permissions in YAML

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

Manage Release permissions in YAML

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

Manage system passwords

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

Security FAQs

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

Security in Stitch

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.

Set up roles and permissions

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

Store credentials

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.

Store encrypted passwords in Deploy

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.

Store proxy servers in Deploy

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.

Store shared host credentials

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.