Hi Andrew,
For most scenario’s that’s enough. If you have a certificate that will not work for a certain host but will for another, you can specify which certificates to use for which hosts using ClientCertificateUsages. Use the host name as an identifier.
There is an even more advanced scenario: use the Client certificate identifier in the Call REST activity if you need to use different client certificates for the same host. In that case, you use other identifiers in ClientCertificateUsages, whatever identifier you see fit. Even “a”, “b”, “c” would work. In Client certificate identifier in the Call REST activity you specify a variable. The running app will use that value as the identifier in the ClientCertificateUsages to find the certificate to use.
For example when the variable has the value “b” and ClientCertificateUsages is { “a”: “mycert.pfx”, “b”: “myothercert.pfx” }, the runtime will use myothercert.pfx