Managing certificates and keys for MDM server installation
To enable secure communication in a BigFix MCM deployment, various certificates and credentials are required for the MDM Server. These include SSL certificates for internal communication, TLS certificates for external security, and credentials for push notification services.
Starting with BigFix MCM 3.3, SSL certificates are automatically generated and managed within WebUI, eliminating the need for manual creation and upload. However, TLS certificates and push notification credentials must still be obtained from third-party sources and uploaded manually.
SSL certificates and keys
MCM v3.3 and Later-
The required SSL certificates and keys are automatically generated and stored within WebUI.
-
No manual creation or upload is required during MDM Server installation.
For users who previously created SSL credentials using older methods (prior to MCM v3.3), the following options remain available.
-
Add Credentials – Allows manually adding SSL credentials.
-
Update Credentials – Enables replacing existing SSL credentials.
-
Remove Credentials – Deletes previously uploaded SSL credentials.
These manual management options will be deprecated in a future release, as they are no longer required for MCM deployment.
BigFix MDM server TLS certificate and key
TLS certificates are required to secure external communication between the MDM Server and managed devices. These certificates must be obtained from a trusted Certificate Authority (CA) and provided in the form of a chain.. The TLS certificate chain is deployed through the MDM Server installation in the WebUI.
TLS certificates are updated through Fixlet 702: BigFix MDM Server - Stage External
TrustedCA TLS Certificates
.
- MDM Server TLS certificate chain with a .crt or .pem extension
- MDM Server TLS private key with a .key extension
- MDM Server TLS private key password
See additional notes at BigFix MDM Server TLS Certificate Content.