
|
If you were logged in you would be able to see more operations.
|
|
|
|
File Attachments:
|
|
|
Environment:
|
Windows XP, Intel Pentium 4
|
|
Issue Links:
|
Reference
|
|
This issue relates to:
|
|
DIRSERVER-169
Incorrect SearchResult name and "compare" failure using CoreContextFactory
|
|
|
|
|
|
|
|
| Resolution Date: |
27/Aug/06 08:07 AM
|
|
There is an entry containing valid X.509 certificate. When I attempt to find that entry by that certificate, search fails. There are two variants of search: one uses 'userCrtificate' attribute name and the other uses 'userCrtificate;certificate' attribute name ('binary' may be specified instead of 'certiifcate' - no change). Attached are log files produced in each of the search attempts.
Case 1:
Java statement:
NamingEnumeration results = ctx.search("ou=users,o=ActiveMQ,dc=example,dc=com", "userCertificate = {0}", new Object[] {cert}, constraints);
produces log as in file ' no-binary.log'
Case 2:
Java statement:
NamingEnumeration results = ctx.search("ou=users,o=ActiveMQ,dc=example,dc=com", "userCertificate;binary = {0}", new Object[] {cert}, constraints);
produces log as in file 'with-binary.log'
|
|
Description
|
There is an entry containing valid X.509 certificate. When I attempt to find that entry by that certificate, search fails. There are two variants of search: one uses 'userCrtificate' attribute name and the other uses 'userCrtificate;certificate' attribute name ('binary' may be specified instead of 'certiifcate' - no change). Attached are log files produced in each of the search attempts.
Case 1:
Java statement:
NamingEnumeration results = ctx.search("ou=users,o=ActiveMQ,dc=example,dc=com", "userCertificate = {0}", new Object[] {cert}, constraints);
produces log as in file ' no-binary.log'
Case 2:
Java statement:
NamingEnumeration results = ctx.search("ou=users,o=ActiveMQ,dc=example,dc=com", "userCertificate;binary = {0}", new Object[] {cert}, constraints);
produces log as in file 'with-binary.log'
|
Show » |
| No work has yet been logged on this issue.
|
|