Anyone seen this before? IE, you add an identity source, the AD server gets demoted yet SSO continues to try and bind to it? I've removed and re-added identity sources, but it continues to try for the demoted server:
In this log - C:\ProgramData\VMware\CIS\logs\vmware-sso\vmware-sts-idmd.log you see:
2014-07-21 09:50:41,562 WARN [ServerUtils] cannot bind connection: [ldap://adserver.domain.COM, null]
2014-07-21 09:50:41,562 ERROR [ServerUtils] cannot establish connection with uri: [ldap://adserver.domain.COM]
5.5 SSO
