Provisioning agents and repeaters with a SHA1 fingerprint of the Application Server self-signed certificate (UNIX)
Use this procedure to create, or update, on each managed server and repeater a file named bladmin. This file contains the SHA1 fingerprint of the Application Server self-signed certificate. An agent or repeater uses this fingerprint to validate the self-signed certificate received from the Application Server during the TLS handshake.
To provision agents and repeaters with a SHA1 fingerprint of the Application Server self-signed certificate
Ensure that the secure file on all managed servers is configured so that
tls_mode=encryption_only. If necessary, generate this setting by running the following
secadmincommand on each agent:
secadmin -m rscd -p 5 -T encryption_only -e tls
You can also run this command using nexec from the Application Server (using
nexec <hostname> secadmin ...) or by using a NSH script job.
Before you can provision a managed server with the fingerprint of the Application Server's certificate, you must ensure that the secure file on the agent or repeater is configured correctly. If you prematurely set the rscd entry in a secure file so that
tls_mode=encryption_and_auth, the agent or repeater will refuse the incoming connection because it will not have the SHA1 fingerprint of the Application Server's self-signed cert. The secure file must have the rscd entry set as shown below when deploying the certificate fingerprint. The secure file is located in the /etc/rsc directory on a UNIX server and C:\<WINDIR>\rsc on Windows, where <WINDIR> is typically windows.
This is the default setting after a fresh installation of an agent, so in most situations there is no need to perform this step.
- Set up root or Administrator privileges on each managed server hosting an agent from the application server host.
To provision an agent or repeater with the SHA1 fingerprint of an Application Server's certificate, you must have root or Administrator privileges on the server hosting the agent. To grant this privilege, update the exports file by creating the following entry:
<appserver hostname> rw,user=Administrator
<appserver hostname> rw,user=root
where <appserver hostname> is the hostname or IP address of the application server host. Ensure that you revert these settings to more restrictive settings after performing the next two steps, as discussed in step 5.
- Using a command line on the Application Server, cd to /opt/bmc/bladelogic/NSH/br/.bladelogic, the directory containing the id.pem file.
- Push the SHA1 fingerprint to managed servers by entering the following command:
/opt/bmc/bladelogic/NSH/sbin/putcert bladmin id.pem <agent1...agentN>
<agent1...agentN>is a space-separated list of the host names or IP addresses (IPv4 or IPv6) of the managed servers hosting agents or repeaters.
This command creates or updates a fingerprint file on each targeted agent or repeater. On a Windows machine, the fingerprint file for a Window Application Server is C:\Program Files\BMC Software\BladeLogic\RSCD\certs\bladmin; on a UNIX machine, the fingerprint file for a Windows Application Server is /opt/bmc/bladelogic/NSH/certs/bladmin.
In environments where multiple Application Servers communicate with agents, you should provision each Application Server with its own self-signed certificate. Performing this procedure for each of those Application Servers generates multiple fingerprints in the bladmin file.
- Revert the setting in the exports file on managed servers back to a more restrictive user mapping. Otherwise, all users accessing those agents from the application server host are mapped to root or Administrator.
Ensure that you keep a backup of the id.pem file. This backup file will enable you to restore communication between the Application Server and your RSCD Agents if the id.pem file is inadvertently removed or changed. See also Backup and restore of the BladeLogic environment.