Trusted Certificate Authorities
Notice: The Certificate Authorities (CAs) listed below are supported by APEX. If you are using a certificate issued by one of these CAs and encounter trust or validation issues, please contact the APEX Support team so that we can investigate.
Trusted CA certificates are onboarded through APEX’s regular maintenance process. As deployments require prior validation and testing in lower environments, requests should be raised at least 2 weeks before a scheduled maintenance window. Requests raised within the 2-week period will be planned for the following maintenance window instead.
For scenarios where this affects Application JWKS registration, publishers may temporarily use the manual JWKS input capability until the required CA certificate has been deployed to APEX.
List of Recommended Trusted Certificate Authorities for APEX Cloud
For publishers to note
Important: The Publisher is accountable for taking appropriate actions to handle and mitigate any potential security threats that may arise due to the usage of non-trusted root Certificate Authorities (CAs) or self-signed certificates, which are not explicitly mentioned in this document. This encompasses addressing any security incidents that may occur as a result of the use of non-trusted root Certificate Authorities (CAs) or self-signed certificates.
Note: APEX does not support the IP address field in the Subject Alternative Name (SAN) of the SSL Trusted Certificate. For more information, refer to the Troubleshooting section.
