Client Management OnPrem/SaaS: SSL certificate warnings may be displayed when accessing the Client Management web interface pages (Windows)

Knowledge Article

Client Management OnPrem/SaaS: SSL certificate warnings may be displayed when accessing the Client Management web interface pages (Windows)
The certificate hasn't been imported into the device trusted root certificates.
BMC Client Management
Client Management
BMC Client Management (all versions) + Windows OS
  1. While accessing MyApps, a warning is displayed or any other page related to the agent web interface. To access to the pages, need to click on "Advanced..." then "Accept the Risk and Continue":

    User-added image


  2. Getting a Certificate warning while accessing Webconsole or any other BCM web page
The Client Management Certificate Authority certificate has not been installed for the devices.

This is being displayed because this certificate is unknown to the system as of now. This is resolved by importing the certificate from the C:\Program Files\BMC Software\Client Management\Master\bin\certs\auth\_CHECKSUM_\BCM.crt. More information here: Client Management: How to identify the certificate authority trusted by the master

1- Windows:

Method A: Manual Certificate Import

  1. Open the folder C:\Program Files\BMC Software\Client Management\Master\bin\certs\auth\<checksum>\BCM.crt. More information here: Client Management: How to identify the certificate authority trusted by the master
  2. Right click on the certificate and select "Install Certificate"
  3. Choose Local Machine in the import dialog and select NEXT
  4. Choose Place all Certification in the following store then browse and select -> Trusted Root Certification Authorities.
  5. Close then reopen the browser and browse to the agent web interface
  6. Make sure the error is not displayed anymore

More information on using the certificate import wizard is available from Microsoft, and for the purposes of this article, steps 5 through 9 from this TechNet blog post can be followed.

Method B: Using MMC snap-in

  1. Run the following command line: "mmc"
  2. Add snap-ins from File > Add/Remove Snap-in > Certificates > Local computer and Users
  3. Go to Certificates > Trusted Root Certification Authority > certificates > Right click > All Tasks > Imports > From C:/Program Files/BMC Software/Client Management/Client /bin/certs/auth 
  4. Click on Data Modified (Choose latest date folder) and choose the .crt file to import. Click Yes.
  5. Run gpupdate /force as an administrator
  6. Close then reopen the browser and browse to the agent web interface
  7. Make sure the error is not displayed anymore


Method C: GPO

The best method, if a domain is available, is to distribute certificates to computers through a GPO.

  1. Make sure that the Active directory does have Active Directory Certificate Services installed.
  2. Click Start, point to Administrative Tools, and then click Group Policy Management.
  3. Then:
    1. Find an existing Group Policy object (GPO) or create a new GPO to contain the certificate settings. Ensure that the GPO is associated with the domain, site, or organizational unit (OU) where the appropriate user and computer accounts reside.
    2. Right-click the GPO, and then click Edit.
    3. In the console tree, open Computer Configuration\Policies\Windows Settings\Security Settings\Public Key Policies, right-click Trusted Root Certification Authorities, and then click Import.
    4. On the Welcome to the Certificate Import Wizard page, click Next.
    5. On the File to Import page, type the path to the appropriate certificate files (for example, our bcm file From C:\Program Files\BMC Software\Client Management\Master\bin\certs\auth\<checksum>\BCM.crt.The correct cert to import may vary and should be verified by reviewing the definition of CertsAuth= in the \Master\config\mtxagent.ini file. More information here: How to identify the authorities trusted by the master
    6. On the Certificate Store page, click Place all certificates in the following store, and then click Next.
    7. On the Completing the Certificate Import Wizard page, verify that the information provided is accurate, and then click Finish.
    8. Run gpupdate /force as an administrator
    9. Close then reopen the browser and browse to the agent web interface
    10. Make sure the error is not displayed anymore


Method D: Through a package:

D1 - Windows
This method can be used if the devices are not in a domain:
- create a package on a windows based package factory
- add the .crt to the package
- in the tab "Configuration" set:
- Overwrite: Yes Yes No Yes
- Destination: set the path to copy the .cert to first
- do not set anything else
- publish the package
- create an operational rule
- add the package to it
- add the step "Execute Program" and set it to run the following command line:
certutil -addstore Root _PATH_TO_CERT_.crt
Where _PATH_TO_CERT_.crt must be replaced by the path to which the crt has been copied by the package, e.g C:/temp/bcm.crt, as per set into the Destination field of the package for this example.
- assign the operational rule to a test device
- Close then reopen the browser and browse to the agent web interface
- Make sure the error is not displayed anymore
 
D2 - Linux
 
- create a package on a mac OS based package factory
- follow the exact same steps than in D1 but the part on the command line
- set the command line in the step "Execute Program" to:
security add-trusted-cert -d -r trustRoot -k "/Library/Keychains/System.keychain" "CertFile.crt"

Note: to learn more about certificates in BCM, refer to this KA: Client Management: About SSL certificates
BMC Client Management
Client Management
BMC Client Management (all versions) + Windows OS
BMC Client Management
Client Management
BMC Client Management (all versions) + Windows OS
Attachment(s):