Identity Broker for Microsoft Active Directory - ability to use SSL with certificate that doesn't match endpoint address

Shane Day (Chief Technology Officer) 10 years ago in UNIFYBroker/Microsoft Active Directory updated by anonymous 9 years ago 2

CloudBroker requires the following:

  • SSL on all communication

IDBAD will fail if the end-point address (a public DNS entry) is different to the certificate supplied by the AD end-point, something that is entirely likely to happen if a customer cannot use their NAT to set up SSL and terminate at that address. For example:

IDBAD is set to connect to unify-demo-idbchrslite-1-ad.cloudapp.net, however the AD certificate is issued by the domain CA which makes the certificate idbpc21-ad.demo.unifysolutions.net.

The AD connector should permit the certificate to be determined by a name in the our configuration. The certificate must still be valid against the local machine certificate store.

The latest version on SUBIDBAD:Downloads has the required settings:

SSL True
Ignore Cert Errors Custom
Certificate Subject Name CN=idbc21p-ad.demo.unifysolutions.net
Allowed Cert Flags RevocationStatusUnknown, OfflineRevocation