|
If you were logged in you would be able to see more operations.
|
|
|
|
File Attachments:
|
| |
Size |
|
example.ldif |
2006-11-07 08:38 AM |
Kirill Kovalenko |
62 kB |
|
|
Environment:
|
Windows XP SP2, Java 1.5.06
|
|
| Resolution Date: |
24/Aug/07 11:57 PM
|
|
When it comes to search attributes with syntax 1.3.6.1.4.1.1466.115.121.1.34, like uniqueMember, the server does not seem to work properly. For example, in my environment, the (uniqueMember=uid=kvaughan,ou=People,dc=example,dc=com) search filter brings the search result while (uniqueMember=uid=kvaughan, ou=People, dc=example, dc=com) does not. The only difference here is spaces between RDN components in the search filter value. Server should normalize uniqueMember values before compare takes place.
|
|
Description
|
When it comes to search attributes with syntax 1.3.6.1.4.1.1466.115.121.1.34, like uniqueMember, the server does not seem to work properly. For example, in my environment, the (uniqueMember=uid=kvaughan,ou=People,dc=example,dc=com) search filter brings the search result while (uniqueMember=uid=kvaughan, ou=People, dc=example, dc=com) does not. The only difference here is spaces between RDN components in the search filter value. Server should normalize uniqueMember values before compare takes place. |
Show » |
| No work has yet been logged on this issue.
|
|
Bug
Closed
Major
uniqueMember attribute compare does not seem to work properly (uniqueMemberMatch is not implemented?)
