MHS Adapter When specifying a domain name, it fails to communicate with SDS

[robert-joscelyne]

MHS Adapter - When specifying a domain name, it fails to communicate with SDS via the Spine Lookup Routine

[tomzo]

There is a configuration environment variable: MHS_SDS_URL

When it is to string like ldap://192.168.128.11:389 the inbound component starts fine. But when it is set to anything which contains a domain name like ldap://example.com:389, the inbound component crashes stating that LDAP url is invalid.

This is especially a critical bug when using ldaps protocol because the certificates returned by the server must match with the domain name, so it's not possible to workaround by using IP then.

[bartek-sarul]

Looks like already tracked under https://gpitbjss.atlassian.net/browse/NIAD-50