[Date Prev][Date Next]
Re: Cannot search usercertificate binary data with raw data
Michael Ströder wrote:
Luis Neves wrote:
but i want to specifie a raw filter to the userCertificate atribute:
Ive uuencoded the original DER certificate and used the result as a
Not sure whether you generated the search filter correctly at all. If you use
uuencode the cert gets base64-encoded?
If you want to search for an octet string you have to use hex-escaping of the
bytes in the search filter. See the escaping rules in RFC 4515.
ldapsearch -x -h 10.15.254.148 -p 389 -D "cn=root,dc=cm-lisboa,dc=pt" -w
***** -s sub -b "ou=AuthzLDAPCertmap,dc=cm-lisboa,dc=pt"
etc etc etc )(objectClass=strongAuthenticationUser))'
But userCertificate has certificateExactMatch (188.8.131.52) defined as equality
matching rule. This is *not* the octetStringMatch (184.108.40.206) matching rule.
Searching certs with octetStringMatch will obviously not perform well though.
I'd recommend to think about another method.
It is legal to use an octet string for certificateExactMatch. In OpenLDAP the
octet string is simply parsed and turned into a certificate assertion value
and then matched as usual.
Probably the encoding of his filter value is just wrong. And of course, it
would be simpler to just use a certificate assertion value instead.
-- Howard Chu
CTO, Symas Corp. http://www.symas.com
Director, Highland Sun http://highlandsun.com/hyc/
Chief Architect, OpenLDAP http://www.openldap.org/project/