Bug #26
DNs containing a space are not correctly parsed
| Status: | Closed | Start: | 13/01/2009 | |
|---|---|---|---|---|
| Priority: | Low | Due date: | ||
| Assigned to: | Jonathan Clarke | % Done: | 100% |
|
| Category: | Core | |||
| Target version: | 1.1.0 | |||
| Problem in version: |
Description
With, for example, in the config file:
8<----------
dn.real_root = ou=Users and Groups,dc=somewhere,dc=org
dst.java.naming.provider.url = ldap://localhost:389/ou=Users and Groups,dc=somewhere,dc=org
8<----------
LSC performs a search on the target dir with base of "ou=Users".
Associated revisions
Automatically escape spaces in JNDI base DN (closes:#26)
History
Updated by Jonathan Clarke over 1 year ago
- Priority changed from Normal to Low
This bug occurs when specifying a base DN in the X.java.naming.provider.url property. A workaround is to quote the spaces with the chain "\\20". For example, the DN "ou=My Users,o=demo" becomes "ou=My\\20Users,o=demo".
As such, this is more a "bug" in JNDI than in the LSC. It might be nice for the LSC wizard to quote such values, however...
Updated by Jonathan Clarke over 1 year ago
- Status changed from New to Closed
- Assigned to set to Jonathan Clarke
- % Done changed from 0 to 100
Closed - the AntInstaller generator now rewrites the base DN to replace spaces with "\\20" in the [src|dst].java.naming.provider.url property written in the config file.
The configuration documentation on the website has also been updated to warn users about this.