I can't start the CA Access Gateway in Secure Cloud

Products

• CA Risk Analytics
• CA Secure Cloud SaaS - Arcot A-OK (WebFort)
• CLOUDMINDER ADVANCED AUTHENTICATION
• CA Secure Cloud SaaS - Advanced Authentication
• CA Secure Cloud SaaS - Identity Management
• CA Secure Cloud SaaS - Single Sign On

Issue/Introduction

Recently deployed a new ssl certificate for the apache server was deployed, because the old one was about to expire. Following that  the CA Access Gateway will not start, as every attempt results in the following message being thrown

Unable to start SSL enabled Apache; not attempting to start Proxy Engine 
Consult stdout or Apache logs for details. 

This article provides some steps to troubleshoot this problem

Environment

CA Access Gateway, all versions

Cause

The most likely cause is a certificate mismatch.

Resolution

 To determine if this is the case, check the httpd logs under /opt/CA/secure-proxy/proxy-engine/logs and look for entries like the following

[Tue Jul 10 09:54:35.139679 2018]  AH02565: Certificate and private key website1.example.com:443:0 from <CA_Access_Gateway_HOME>/SSL/certs/ServerCertificate.cer and <CA_Access_Gateway_HOME>/SSL/keys/website2.example.com.key do not match 
AH00016: Configuration Failed 

[Tue Jul 10 09:54:35.139679 2018] [ssl:emerg] [pid 18661:tid 4151437056] AH02565: Certificate and private key xxx.xx.xxx:443:0 from <CA_Access_Gateway_HOME>/SSL/certs/ServerCertificate.cer and /opt/CA/secure-proxy/SSL/keys/website2.example.com.key do not match 
AH00016: Configuration Failed 

Make sure that the public and private key you have specified for the new ssl configuration match. 

Additional Information

To configure or replace a ssl certificate for the apache server of a CA Access Gateway (SPS) machine, please see

https://techdocs.broadcom.com/us/en/symantec-security-software/identity-security/siteminder/12-8/configuring/access-gateway-configuration/configuring-ssl-for-access-gateway.html