In this section we will cover how to create your first cloud certificate authority. We will cover the different types of CAs, how to create your first root CA, how to create your first subordinate CA, and for people that are looking to modernize or manage their certificates in Windows AD Certificate Services how to connect your first ADCS CA to EZCA.
In cryptography a certificate authority or certification authority (CA) is an entity that issues digital certificates. A digital certificate certifies the ownership of a public key by the named subject of the certificate.
The key difference between a publicly trusted and private certificate authority is that all computers and browsers trust publicly trusted Certificate Authorities while private CAs will have to be explicitly added by the IT administrator.
The two tier hierarchy has two CA types Root CA and Issuing/Subordinate CA. This article explains what is the difference between a root CA and an Issuing CA.
A Root CA is needed to be the root of trust for your PKI Deployment. In this page we will guide you on how you can create your own Root CA either using EZCA or creating your own offline CA.
In this page we will guide you on how you can create your own Issuing SSL CA and chain it up to a Root CA (EZCA Root or Offline Root).
This page will walk you through how to create an Azure based SCEP CA to issue SSL Certificates for your Intune managed devices.
In this page we will show you how to connect to GlobalSign to issue and automate public SSL certificate lifecycle using the EZCA and all the integrations it offers.
When deciding the lifetime of your certificates, the selected key size and cryptographic algorithm have an effect on how long the certificate will be safe.
When designing the validity period of a Certificate Authority (CA), many factors have to be taken into consideration Lifetime of the parent CA, desired lifetime for issued certificates, key algorithm used, and security of the private key.
In this page we will guide you on how you can create your own Issuing SSL CA and chain it up to a Root CA (EZCA Root or Offline Root).