Home
Managing security
HCL Launch 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.
Updating LDAP users and groups
LDAP users' name, addresses, and groups can be updated.

Managing security
HCL Launch 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
    To create an authentication realm on the server, specify where to store information about the users, such as internal storage on the server, a single sign-on service, or on an LDAP server.
  - Creating users manually
    You can manually create users on the server for internal security and SSO type authentication realms.
  - Editing user information manually
    You can manually edit the stored name, email address, and password 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).
  - 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.
- Roles and permissions
  A role is a list of permissions that users have on the HCL Launch 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.
- 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 Launch server and external services.

Updating LDAP users and groups

LDAP users' name, addresses, and groups can be updated.

About this task

LDAP users and groups can be updated in following ways:

LDAP or Active Directory Authentication Realms using LDAP authorization realms to update names and email addresses.
SSO authentication realms using LDAP authorization realms to update groups. Names and email addresses are updated when user logs-in through SSO.

Note: You can not update users or groups if there is no LDAP Authorization realms being used.

Procedure

On the server, click Settings > Authentication (Users) > select LDAP/SSO realm > Update Users for the LDAP authentication realm to use.
In the Update All Users dialog box, click Submit to update the LDAP user information for the selected LDAP or SSO realm.
The names, email addresses, and/or groups for all users in the realm are updated.
Note: User information is also synced when a user logs-in manually from the LDAP or Active Directory.