An LDAP OU Definition that contains a RDN with an ampersand ("&") makes the MID Server failing to browse or read the data. - Known Error

An LDAP OU Definition that contains a RDN with an ampersand ("&") makes the MID Server failing to browse or read the data. Description Using an LDAP OU Definition that contains an ampersand (&) will fail to retrieve data or browse it.

Steps to Reproduce

On the LDAP server, create a branch called "ASP People & PCs" and add a few users.

For more information, see the product documentation topic .

Create a new LDAP server and add a new OU Definition with RDN = ASP People & PCs.

Complete the required fields and click Save.

Select Browse.

The RDN shows as truncated and no results are returned.

The localhost will contain the following messages:

01/12/16 13:43:34 (444) Probe: LDAPBrowseProbe:b729126137481208b14fa9c2b3990e17 Worker starting: LDAPBrowseProbe source: b729126137481208b14fa9c2b3990e17&#13; 01/12/16 13:43:34 (585) Probe: LDAPBrowseProbe:b729126137481208b14fa9c2b3990e17 DEBUG: LDAP is ready for browsing for: *&#13; 01/12/16 13:43:34 (694) Probe: LDAPBrowseProbe:b729126137481208b14fa9c2b3990e17 [LDAP: error code 32 - 0000208D: NameErr: DSID-031001E4, problem 2001 (NO_OBJECT), data 0, best match of: 'DC=service-now,DC=com' ]&#13; 01/12/16 13:43:34 (694) Probe: LDAPBrowseProbe:b729126137481208b14fa9c2b3990e17 AD Naming Error&#13; 01/12/16 13:43:34 (694) Probe: LDAPBrowseProbe:b729126137481208b14fa9c2b3990e17 Invalid Hierarchy: 'OU=ASP People , DC=service-now, DC=com' does not exist within 'DC=service-now, DC=com'&#13; 01/12/16 13:43:34 (694) Probe: LDAPBrowseProbe:b729126137481208b14fa9c2b3990e17 SEVERE *** ERROR *** LDAP exception processing results&#13; java.lang.NullPointerException&#13; at com.service_now.mid.probe.LDAPBrowseProbe.createECCQueueRowElement(LDAPBrowseProbe.java:149)&#13; at com.service_now.mid.probe.LDAPBrowseProbe.doWork(LDAPBrowseProbe.java:91)&#13; at com.service_now.mid.probe.LDAPBrowseProbe.probe(LDAPBrowseProbe.java:74)&#13; at com.service_now.mid.probe.AProbe.process(AProbe.java:66)&#13; at com.service_now.mid.queue_worker.AWorker.runWorker(AWorker.java:104)&#13; at com.service_now.mid.queue_worker.AManagedThread.run(AManagedThread.java:36)&#13; &#13;

Workaround On the LDAP server, change the symbol '&' to the word 'and'. Then fix the value on the LDAP OU Definition. Or do not use a MID server if you need to use an LDAP OU Definition with a RDN containing an ampersand (&).