So my ldapsearch works great, except for some results I found today. My search is:
/usr/lib64/mozldap/ldapsearch -T -h 10.1.1.1 -p 3891 -D "uid=datapower,ou=People,dc=blah,dc=com" -w xxxxxx -b "ou=Certs,dc=blah,dc=com" "(&(x509ValidityNotAfter<=20170623132953Z)(x509ValidityNotAfter>=20170522132953Z))" FSID X509SerialNumber x509ValidityNotAfter X509Issuer
Almost everything returns just fine:
dn: x509oid=1430833298883,ou=Certs,dc=com
X509SerialNumber: 65794219962985063522072255299762693016
FSID: F00PCF
X509Issuer: CN=GeoTrust SSL CA - G3, O=GeoTrust Inc., C=US
x509ValidityNotAfter: 20170620235959Z
But some results have many multiple matching attributes (FSID). Nearly all return good results, but for this one it returns a bunch of values that are base 64 encoded (see below Rj*....). Any idea why it would just chose to do so on this one (I've went directly to ldap and those attribute values are not in base64):
dn: x509oid=1443642301854,ou=Certs,dc=routeone,dc=com
x509ValidityNotAfter: 20170618240000Z
X509SerialNumber: 237747983070111291030884597428865776599352552985
FSID:: RjAwMEhGIA==
FSID:: RjAwMEhHIA==
FSID:: RjAwMEhIIA==
FSID:: RjBUQzAwIA==
FSID:: RjBUQzAxIA==
FSID:: RjBUQzAyIA==
FSID:: RjBUQzAzIA==
FSID:: RjBUQzA0IA==
FSID:: RjBUQzA1IA==
FSID:: RjBUQzA2IA==
FSID:: RjBUQzQzIA==
FSID:: RjBUQzQ0IA==
FSID:: RjBUQzQ1IA==
FSID: F0TC46
FSID: FTC001
FSID: FTC002
FSID: FTC003
FSID: FTC004
FSID: FTC005
---------- Post updated at 08:43 AM ---------- Previous update was at 08:40 AM ----------
oh, would the ' -B ' option be the ticket?
It seems to return what I need
---------- Post updated at 10:27 AM ---------- Previous update was at 09:43 AM ----------
yup, that was it. using the -B option gets rid of the base64 encoded values for some reason.