OU limitation in the LDAP search

[Ali Amir]

Hi guys,

is there any OU count/string limitation in the searchBases?

For example:

   <SearchBase1>ou=_Cities,DC=GLOBAL,DC=INTERN,DC=test-domain,DC=COM</SearchBase1>
   <BDISearchBase1>ou=_Cities,DC=GLOBAL,DC=INTERN,DC=test-domain,DC=COM</BDISearchBase1>
   <BDISearchBase2>dc=sanjose,dc=intern,dc=test-domain,dc=com</BDISearchBase2>
   <SearchBase2>dc=sanjose,dc=intern,dc=test-domain,dc=com</SearchBase2>
   <BDISearchBase3>OU=Contacts,OU=Mail Objects,OU=_Global Resources,DC=GLOBAL,DC=INTERN,DC=test-domain,DC=COM</BDISearchBase3>
   <SearchBase3>OU=Contacts,OU=Mail Objects,OU=_Global Resources,DC=GLOBAL,DC=INTERN,DC=test-domain,DC=COM</SearchBase3>

Is that fine to have three OU in the searchBase3?

Could an OU have a blank character like "Mail Objects"?

[Jaime Valencia]

5 Search base

http://www.cisco.com/c/en/us/td/docs/voice_ip_comm/jabber/11_6/cjab_b_parameters-reference-guide-for-cisco/cjab_b_parameters-reference-guide-for-cisco_chapter_01010.html#CJAB_RF_E7A88F99_00

[Ali Amir]

I did check this guide.

I just want to know about the limitation of OU in a SearchBase.

In my example I have three OU in a search space (SearchBase3)

1- OU=Contacts

2- OU=Mail Objects

3- _Global Resources

and two of OU have a space. Is a normal space acceptable in the search query or should I put &nbsp; as space (for ampersand we put normally &amp;).