Actalis solutions to continue using clientAuth
Analyzing use cases makes it possible to quickly identify the most suitable certificate.
Below is an operational summary.
1. If only clientAuth is required, and the certificate does NOT need to be trusted in browsers, the recommended solution is:
- Actalis SSL Client Certificates
This is the simplest and most natural choice for this type of need. These certificates have a specific profile for TLS Client Authentication and are fully exempt from browser vendor and CAB Forum requirements. Discover
2. If only clientAuth is required but the certificate MUST be trusted in browsers, the recommended solution is:
- Actalis S/MIME Certificates
An S/MIME certificate can include clientAuth and is issued under a publicly trusted root. Discover
3. If an SSL server certificate is required that also includes clientAuth and must be issued by a recognized CA, the recommended solution is:
For regulated environments or specific use cases requiring an SSL server certificate that also supports client authentication (clientAuth), Actalis offers a solution based on QWAC certificates designed for environments where certificate trust is managed independently of browser trust programs.
For more information about QWAC certificates, visit our dedicated product page.
If you have this requirement, please contact us for more information and to find the solution that best meets your needs.