A <cfldap> search on an IBM Tivoli Directory Server (LDAP), pulling a "binary - octet string" syntax attribute (OID 1.3.6.1.4.1.6054.1.1.31 SYNTAX 1.3.6.1.4.1.1466.115.121.1.5) returns [empty string] when the attribute field is set to the attribute name, which is "erentitlements". The string is not empty - it contains XML data that is correctly returned when the attribute field is set to "*".
| CODE |
|---|
<cfldap action="QUERY" name="entitlements" attributes="*" separator="^" referral="1" start="dc=abc,dc=def" scope="base" server="1.2.3.4" port=389" secure="636" sortControl="asc" username="cn=root" password="********"> <cfdump var="#entitlements#" label="ALL"> |
Returns...
| CODE |
|---|
<cfldap action="QUERY" name="entitlements" attributes="erentitlements" separator="^" referral="1" start="dc=abc,dc=def" scope="base" server="1.2.3.4" port=389" secure="636" sortControl="asc" username="cn=root" password="********"> <cfdump var="#entitlements#" label="ERENTITLEMENTS"> |
Returns...
Even if I remove the XML-like data and replace with a pure text string like "asdf", I still get the [empty string] result.
Packet analyzer tools prove that the data is making it back to the CF server.
Might I have missed a setting that allows binary-like data to be returned outside of a "*" call with <cfldap>? Any ideas? For the record, this worked for me in 2013. I have not used this tool for 3 years, so when I rebuilt my CF server, I installed 2018 and discovered this. So I reinstalled CF10, only to find that it now produces the same result. I'm back on 2018 now.
Thanks!
AdChoices