Workspace ONE UEM is flexible with PKI integration by being able to request certificates from either internal or external certificate authorities (CA). Integrate with GlobalSign PKI services to issue certificates for your Workspace ONE UEM MDM solution.
In order for Workspace ONE UEM to communicate with GlobalSign for certificate distribution, you must have a GlobalSign instance configured and ready to issue certificates. You can then configure Workspace ONE UEM to communicate with GlobalSign using basic authentication. Once communication is successfully established, you can define how to deploy certificates to devices. Below is an example of how GlobalSign and Workspace ONE UEM can be deployed.
|Profile ID||Enter the GlobalSign profile identity bound to the certificate.|
|Product Code||Enter the code for the certificate and the license.|
|Validity Period||Enter how long the certificate is valid.|
|SAN Type||Select Add to include one or more Subject Alternate Names with the template.
This entry is used for additional unique certificate identification. In most cases, this needs to match the certificate template on the server. Use the drop-down menu to select the SAN Type and enter the subject alternate name in the corresponding data entry field.
Each field supports lookup values. Email Address, User Principal Name, and DNS Name are supported by GlobalSign templates by default.
|Automatic Certificate Renewal||Select the checkbox if Workspace ONE UEM is going to automatically request the certificate to be renewed by GlobalSign when it expires.
If you select this option, enter the number of days prior to expiration before Workspace ONE UEM automatically requests GlobalSign to reissue the certificate in the Auto Renewal Period (days) field. This requires the certificate profile on GlobalSign to have the Duplicated Certificates setting enabled.
|Enable Certificate Revocation||Select the checkbox if you want Workspace ONE UEM to be able to revoke certificates.|
Review some tips and troubleshooting steps for the integration. * Verify ability to perform certificate authentication without Workspace ONE UEM.
Remove Workspace ONE UEM from the configuration and manually configure a device to connect to your network server using certificate authentication. This should work outside of Workspace ONE UEM and until this works properly, Workspace ONE UEM will not be able to configure a device to connect with a certificate. * Verify ability to perform certificate authentication with Workspace ONE UEM.
You can confirm that the certificate is usable by pushing a profile to the device and testing whether or not the device is able to connect and sync to the configured EAS, VPN, or Wi-Fi access-point. If the device is not connecting and shows a message that the certificate cannot be authenticated or the account cannot connect then there is a problem in the configuration. Below are some helpful troubleshooting checks. * If SSL TLS errors are received while creating a template. * This error can occur when you attempt two tasks. * Create a Workspace ONE UEM certificate template byselecting the Retrieve Profiles button or * Retrieve a certificate from the Workspace ONE UEM console from the SecureAuth certificate authority. * The troubleshooting technique that usually resolves this problem is adding the required server certificate chain in the console servers trusted root key store. * If the Workspace ONE UEM Certificate Profile fails to install on the device. * Inform Workspace ONE UEM Professional Services of the error and request they: * Turn On Verbose Mode to capture additional data. * Retrieve web console log. * Workspace ONE UEM analyzes the log and works with customer to resolve the problem. * If the certificate is not populated in the View XML option of the profile. * Confirm that lookup values configured on the GlobalSign certificate profile match the look up values in the Workspace ONE UEM console’s Request Template. * Confirm that lookup values in Workspace ONE UEM Request Template are actually populated in the user information being pulled from AD. * Confirm you are pointing to the right profile in GlobalSign.