Hi, My issue is similar to the discussion on this other thread.
I was told that we had a proxy that was connecting to a backend server, and the backend server did not have a certificate, so I started to do some troubleshooting.
I created a targetServer like this:
{
"host": "revoked.badssl.com",
"isEnabled": true,
"name": "badssl-testing",
"port": 443,
"sSLInfo": {
"ciphers": [],
"clientAuthEnabled": "false",
"commonName": {
"value": "*.badssl.com",
"wildcardMatch": true
},
"enabled": "true",
"ignoreValidationErrors": false,
"protocols": [],
"trustStore": "trustStore-outbound"
}
}
<HTTPTargetConnection>
<LoadBalancer>
<Server name="badssl-testing"/>
</LoadBalancer>
<Path/>
</HTTPTargetConnection>
However, I still get a '200 OK' response from the proxy.The trace shows that a successful HTTPS connection was established:
Have I missed something? As far as I can tell, this should not be working, yet it does.
Solved! Go to Solution.
After double-checking, I can confirm that Apigee doesn’t support CRL (Certificate Revocation Lists) or OCSP (Online Certificate Status Protocol) for revocation checking. This means that Apigee will validate the presented certificate against the trustStore, but it won’t automatically check whether the certificate has been revoked.
To monitor the status of certificates, many organizations rely on corporate CAs, which typically provide notifications for revoked or expired certificates. Additionally, enterprises often use Certificate Lifecycle Management (CLM) platforms, which offer centralized monitoring for revocation, expiration, and other issues. These platforms provide features like automated alerts and revocation status tracking through external APIs or CA endpoints.
Without these built-in checks in Apigee, you’ll need to rely on external monitoring solutions or manual certificate audits to stay informed about the status of your certificates.