Hello all,

CP4I 16.1.0.1, API Connect 10.0.8.0, IDG 10.6.0.1. 

We use several TLS client profiles for some of our APIs, all are defined and shared through the Cloud Manager for more centralized management.

This has worked fine until recently, when we added a new TLS client profile, published the associated product and started receiving 500 internal server errors when trying to call the API. Looking on DataPower I can see that TLS client profile has not been created on DataPower. Thinking this a fluke, I created a second TLS cp and observed the exact same result.

The TLS cp in question only has an associated truststore which is used in one other TLS cp, we do not need a keystore for this API. Are there any limitations associated with TLS cp's? Can one truststore be used in multiple TLS client profiles? And when exactly are the TLS client profiles populated to DataPower? Is it when the calling product/API is published or when the TLS cp is created? What could cause the TLS cp object (and idcred, certificate, etc.) to not be created on IDG?

Much thanks for any ideas or comments, we have been banging our collective heads against the wall trying to figure this one out.

Regards,