- BEMS Core service
- Steps to configure the BEMS-Core
- Importing CA Certificates for BEMS
- Importing and configuring certificates
- Replacing the autogenerated SSL certificate
- Configuring HTTPS for BEMS to the BlackBerry Proxy or Good Proxy server
- Assign the BEMS SSL certificate to users
- Keystore commands
- Add dashboard administrators
- BEMS-Core database
- Configure the BlackBerry Dynamics server in BEMS
- Configure a web proxy server
- Enabling log file compression
- Uploading BEMS log and statistical information
- Firebase Push Notifications
- Enabling FIPS Mode in BEMS
- Configuring BlackBerry Dynamics Launcher
- Next steps
- Appendix: Java Memory Settings
- Appendix: Server-side services
- BlackBerry Docs
- BlackBerry Enterprise Mobility Server 3.6
- Configuring BEMS-Core
- Enabling FIPS Mode in BEMS
Enabling FIPS Mode in BEMS
BEMS
BEMS-Core
, BEMS-Mail
, BEMS-Docs
, BEMS-Connect
, and BEMS-Presence
services can be configured to use FIPS 140-2 (U.S. Federal Information Processing Standards) compliant algorithms for cryptographic operations. When FIPS-compliance mode is enabled on one BEMS
instance in a cluster, all instances in the cluster are enabled. To enable this feature in the cluster, all BEMS
nodes must be running the same version of BEMS
(for example, BEMS
2.12 or later). By default, FIPS 140-2 compliant mode is disabled. BEMS
doesn't verify if the OS that hosts the BEMS-Docs
service is running in FIPS 140-2 compliant mode.