FAQs
Those might have popped-up in your mind.
Categories
How to Install Root & Intermediate CA Certificates on Android ?
Please follow the below steps.
Android 11+ Device
In Android 11+, to install a CA certificate, users need to manually:
- Open Device settings
- Go to ‘Security’
- Go to ‘Encryption & Credentials’
- Go to ‘Install from storage’ or ‘Install a certificate’ (depending on devices)
- Select ‘CA Certificate’ from the list of types available
- Accept a warning alert.
- Browse to the certificate file on the device and open it
- Confirm the certificate installation
Samsung Device:
Settings:
- Biometrics and security
- Other security settings
- Install from device storage
- CA Certificate
- Install Anyway
Tagged In
No Comments Yet.
How to quickly install CA certificates automatically on large number of Windows PCs ?
One can use Microsoft Group Policy to install SecureNT CA certificates on large number of PCs automatically. Here is link to our blog which explains how to do it.
No Comments Yet.
Are SecureNT Root Certificates trusted by the browsers ?
Intranet SSL certificate’s root certificate chain is not trusted by default on popular browsers like Chrome, Edge, Internet Explorer, Safari, Firefox, etc. This means that unless certain steps are taken, a client PC will get a “certificate not trusted” error when a user uses a web browser to access a website hosted on a Server with Intranet SSL.
But these steps (installation of SecureNT CA root certificates) need to be taken once only. After those steps are taken, the client PC will always trust the Intranet SSL certificate.
You can find the steps here.
Tagged In
No Comments Yet.
Why do I need to install the CA cert on the client desktops also ?
It’s a good question. If public CA could issue SSL certificates for internal names like local hosts, IP addresses, or server names then we - Private Certifying Authority (CA) - won’t exist.
We issue SSL certificates to local hosts, server names, IP addresses and internal URLs. They are SSL certificates for internal network names. And our CA certificates are not trusted by the browsers and the client Operating Systems like Windows.
Reason for this situation is that CA/browser Forum which governs Public Certifying Authorities (CA) decided in 2015 that public CA can’t issue SSL certificates to Internal Names and internal IP addresses. See this file for details.
Hence Public CAs like Let’s Encrypt, DigiCert, GlobalSign, EnTrust etc. can’t issue SSL certificates for internal networks.
So, who so ever issues SSL for Internal Names or internal IP addresses have to issue them with non-public/Private CA roots only.
When you use such SSL certificates Operating System vendors and browsers don’t trust them because of CA Browser Forum’s policy. So, for browser to trust them customer needs to install Private CA roots on to each client device.
- It's simple and takes hardly 10-15 seconds to install.
- It has to be done once only.
- If you have many devices then you can use Microsoft Group Policy to install on all connected devices in a few minutes.
- No matter who supplies your Intranet SSL, this technical requirement will always be there.
- All our customers do it because it gives them peace of mind.
It’s super easy to install using Microsoft Group Policy. See our blog page for details.
Our customers use SecureNT Intranet SSL certificates for internal web application like ERP, Email, HRMS, CRM, Service Desk, Analytics, etc and so on. These are very critical applications for their business. So, due to our certificates important flowing on the internal networks is encrypted. And their data is protected from the hackers and employees with wrong intentions.
Tagged In
No Comments Yet.
Categories
Tags