Security considerations for HCL UrbanCode Deploy#
You can act to ensure that your installation is secure and set up user access controls.
- Enabling security during the installation process
- Enabling secure communication between multiple applications
- Ports, protocols, and services
- Keystores for SSL communication and for encrypting secure properties
- Customizing your security settings
- Setting up user roles and access
Enabling security during the installation process#
During the installation process, by default the server is configured to use Secure Sockets Layer (SSL) for secure communication. The server is configured to use SSL in both manual and silent installations. In addition to SSL communication, role-based access controls are available that determine what actions a particular user can do.
In general, you configure security on the application server or the database server, not in HCL™ Launch. HCL Launch communicates with the database by using the Java™ Database Connectivity (JDBC) provider on the application server.
To learn about configuring Lightweight Directory Access Protocol (LDAP) authentication, see Authentication realms.
Installing a FIPS-compliant server#
You can configure a Federal Information Processing Standards (FIPS) compliant server by specifying options at installation time. A FIPS-compliant server has certain limitations. See Installing the server in interactive mode.
Enabling secure communication between multiple applications#
You can use tokens to secure communications between products that integrate with HCL Launch. To learn more about tokens, see Tokens.
Ports, protocols, and services#
The following table shows the default port numbers for the server.
|Port type||Default port number|
|Incoming connections to the server web interface (HTTP)||8080|
|Incoming connections to the server web interface (HTTPS)||8443|
|Java Message Service (JMS)||7918|
|Communication with the Rational® Common Licensing server||Port 27000 for the
The following table shows the default port numbers for the blueprint design server and engine.
Note: If you install the HCL Launch server and the blueprint design server on the same computer, ensure that only one server uses port 8080 and port 8443.
|Port type||Default port number|
|Incoming connections to the blueprint designer web interface (HTTP)||8080|
|Incoming connections to the blueprint designer web interface (HTTPS)||8443|
|Incoming connections to the engine||8004, 8000, 8003, and RPC ports|
|Incoming connections to the cloud discovery service||7575|
The blueprint design server must also be able to create outgoing connections to cloud systems, the engine, the cloud discovery service, and the database. The communication with the Rational Common Licensing server uses port 27000 for the
lmrgd daemon. The port numbers for the vendor daemon can change, but are typically between 27001 and 27009. See your Rational Common Licensing server for the active ports.
In most cases, the blueprint design server accesses the cloud discovery service on local port 7575, and no firewall rules are required. However, if the blueprint design server uses the host name of the machine, you may need to provide access to port 7575 on the firewall.
Keystores for SSL communication and for encrypting secure properties#
HCL Launch supports multiple keystores, which support different security features. The following list describes the default keystores.
The certificate for SSL communication on the HTTPS port of the HCL™ Launch server is stored in the tomcat.keystore file.
The certificate for SSL communication on the JMS port is stored in the server.keystore file. If mutual authentication is enabled, the identities of the server and agent computers are verified. If mutual authentication is disabled, then the server.keystore file is used only to encrypt network traffic. By default, mutual authentication is disabled.
Mutual authentication is not needed with web agents, therefore is deprecated starting in HCL™ Launch version 7.0.0.
The secret key that is used to encrypt and decrypt secure properties is stored in the encryption.keystore file. If you export applications and components that use secure properties to other HCL™ Launch servers, you must exchange the contents of this keystore between the servers. The secret key in the encryption.keystore file is randomly generated during installation. The password is stored in the
encryption.keystore.passwordproperty, and its initial value is the same as the
tomcat.keystore on the blueprint design server
The blueprint design server also has a keystore that is named tomcat.keystore. The blueprint design server keystore contains the certificate for SSL communication on the HTTPS port of the blueprint design server. The default location is server_install/opt/tomcat/conf/tomcat.keystore, where server_install is the installation folder of the blueprint design server.
For more information on keystores and certificates, see Configuring SSL on Apache Tomcat and LDAP servers.
Customizing your security settings#
The only user IDs that are created by default are admin for the server and ucdpadmin for the blueprint designer. To change the password for admin, in the server, click Settings > Authentication (Users). To change the password for ucdpadmin, click Settings > Users and select the Internal Authentication authentication realm.
Failed login attempts are stored in the database. Except for the default admin password, all passwords are stored in encrypted form in the database. After you change the default admin password, it is also stored in encrypted form.
Setting up user roles and access#
You can create and delete users and add users to groups and teams in HCL Launch. To learn more, see Managing security. On the server, the superuser account with special security privileges is admin. On the blueprint editor, the superuser account with special security privileges is ucdpadmin.
The HCL Launch server and the blueprint designer have separate lists of users and teams.
Parent topic: Overview