Welcome
Managing Security
HCL DevOps Deploy (Deploy) uses a flexible team-based and role-based security model that maps to your organizational structure.
Authentication realms
Authentication realms manage users and determine user identity within authorization realms for the server.
Enforcing a maximum login duration
You can enforce a maximum login duration to require users to re-authenticate after a specific period, regardless of the user activity. This setting is useful for organizations whose security policies prohibit persistent login sessions.

Release Notes
This section includes what's new, defect fixes, and deprecations and removals in all releases.
System Requirements
This document includes information about the hardware, containers, prerequisite software, supported operating system, and database requirements with component level detail for the HCL DevOps Deploy (Deploy).
Getting Started
Quickly become productive with HCL DevOps Deploy (Deploy).
Installing
An HCL DevOps Deploy (Deploy) installation consists of a Deploy server, a database server, and at least one agent.
Upgrading and Migrating
Stay updated with latest features and functionalities by upgrading HCL DevOps Deploy (Deploy) server, agents, and relays. This section also provides instruction on how to migrate your Deploy instance.
Integrating
HCL DevOps Deploy (Deploy) supports integrations with other IBM® and HCL products, products from others, and certain cloud systems.
Administering
Learn how to administer settings in HCL DevOps Deploy (Deploy) elements and communication between the elements.
Managing Security
HCL DevOps Deploy (Deploy) uses a flexible team-based and role-based security model that maps to your organizational structure.
- Guidelines for setting up server security
  Although there is no single best way to set up security for the server, the following steps are sufficient in most cases.
- SSL configuration
  With Secure Sockets Layer (SSL) technology, clients and servers can communicate securely by encrypting all communications. Data is encrypted before it is sent and decrypted by the recipient. This communication cannot be deciphered or modified by third-parties. In addition to encryption, SSL can also support authentication.
- Encryption key tools
  Using the encryption key tools, you can manage your encryption keys.
- Authorization realms
  Use the Authorization Realms pane to create authorization realms and user groups for the server. Groups can be imported from external systems, such as LDAP.
- Authentication realms
  Authentication realms manage users and determine user identity within authorization realms for the server.
  - Creating authentication realms
    Use authentication realms to manage users and determine their identity within authorization realms.
  - Creating users manually
    You can manually create users on the server for internal security and SSO type authentication realms.
  - Importing LDAP users
    On the server, LDAP authentication realm users are imported from external LDAP systems.
  - Updating LDAP users and groups
    LDAP users' name, addresses, and groups can be updated.
  - Editing user information manually
    You can manually edit the stored name, email address, password, and additional settings for user accounts on the server for internal security realms. For an SSO authentication realm, name and email address are passed in via HTTP headers (for example, from an HTTP proxy that is translating Kerberos tokens into HTTP headers).
  - Locking and deleting user accounts automatically
    As part of your secured user account management process, you can configure the system to lock and delete idle or inactive users automatically.
  - Enforcing a maximum login duration
    You can enforce a maximum login duration to require users to re-authenticate after a specific period, regardless of the user activity. This setting is useful for organizations whose security policies prohibit persistent login sessions.
- Roles and permissions
  A role is a list of permissions that users have on the HCL DevOps Deploy (Deploy) server. These permissions include the ability to create, edit, and delete objects, such as applications, environments, and components. The permission also includes the parts of the server interface that users can access.
- Secret stores
  You can store user credentials in Hashicorp Vault and integrate with HCL DevOps Deploy (Deploy) to retrieve values from the Vault.
- Security teams
  Users and groups on the server are assigned roles when they are added to teams.
- Security types
  Security types define categories of objects on the server. You can put all objects into a single category, or you can put them in separate categories and give roles different access rights to different categories.
- Tokens
  Tokens provide authorization for agents, agent relays, users, and external systems or applications from the server. Agents use tokens when they run process steps and communicate with the HCL DevOps Deploy (Deploy) server and external services.
- FIPS mode enablement
  You can enable Federal Information Processing Standards (FIPS) mode on the systems that run the HCL DevOps Deploy (Deploy) server, agent, and relays to make them FIPS compliant.
Modeling Software Deployment
Modeling software deployment in HCL DevOps Deploy (Deploy) includes configuring components and component processes and adding those components to applications. Then, you use processes to deploy the components to environments.
Deploying
Learn how to deploy applications in HCL DevOps Deploy (Deploy).
Reporting
Provides several different deployment and security reports.
Extending Product Function
Learn how to extend the function of HCL DevOps Deploy (Deploy).
Troubleshooting and Support
Learn how to troubleshoot some common issues with HCL DevOps Deploy (Deploy).
Security Considerations
You can act to ensure that your installation is secure and set up user access controls.

Enforcing a maximum login duration

You can enforce a maximum login duration to require users to re-authenticate after a specific period, regardless of the user activity. This setting is useful for organizations whose security policies prohibit persistent login sessions.

About this task

The Maximum Login Time setting overrides the Remember me configuration. After this setting is active, a countdown timer is displayed in the log-off menu. The system provides the following visual warnings:

Procedure

In the Web UI, navigate to Settings > System Settings > Security settings.
In the Maximum Login time (hours) field, specify the number of hours users may remain logged in.

Note:
If the value is set to 0 or a negative number, the maximum login time enforcement is disabled.
Save the settings.
Log out and log back into the Web UI.

Note:
Changes to this setting only apply to new sessions. Existing active sessions remain unchanged until the user logs out and back in.

Results

The maximum login time is enforced. When the timer reaches zero, the following actions occur: