The web client requires the SMS Root CA as well as the certificate from the Historian.
What would the best practice be to get these deployed to the users?
The web client requires the SMS Root CA as well as the certificate from the Historian.
What would the best practice be to get these deployed to the users?
Hi Marcell,
Optimal would be that your devices are part of a domain, and that the certificate is deployed using a GPO.
(https://learn.microsoft.com/en-us/windows-server/identity/ad-fs/deployment/distribute-certificates-to-client-computers-by-using-group-policy)
In some cases the customer has a company wide certificate that is already in place and you replace the ASB certificate with the customer specific cert using configurator. (Keep an eye out for the expiration date of the customer cert. in that case).
If your devices are an Android/IOS device, I believe it has to be installed manually to work.
But I must admit that I'm still learning in this quite complex world of certificates, expiration dates and redundant SMS servers, so the discussion is highly appreciated.
Hi Marcell,
Optimal would be that your devices are part of a domain, and that the certificate is deployed using a GPO.
(https://learn.microsoft.com/en-us/windows-server/identity/ad-fs/deployment/distribute-certificates-to-client-computers-by-using-group-policy)
In some cases the customer has a company wide certificate that is already in place and you replace the ASB certificate with the customer specific cert using configurator. (Keep an eye out for the expiration date of the customer cert. in that case).
If your devices are an Android/IOS device, I believe it has to be installed manually to work.
But I must admit that I'm still learning in this quite complex world of certificates, expiration dates and redundant SMS servers, so the discussion is highly appreciated.