[Date Prev][Date Next]
[Chronological]
[Thread]
[Top]
back-sql auxiliary objectClass attributes -> binary value syntax check?
- To: OpenLDAP-software@OpenLDAP.org
- Subject: back-sql auxiliary objectClass attributes -> binary value syntax check?
- From: Babak Nasri <babak.nasri@authentidate.de>
- Date: Mon, 19 Apr 2004 19:24:53 +0200
- User-agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.5) Gecko/20031107 Debian/1.5-3
Having back-sql with iODBC and mysql deployed and set the debugging on,
I realized that auxiliary objeclass(s) -those not mapped through
ldap_entries.oc_map_id rather through ldap_entry_objclasses.oc_name-
is only to represent the objectClass attribute of the main entry and a
further attribute mapping fetch was not to be seen for those
objectclasses in case they apply , although the ldap_oc_mappings and
ldap_attr_mappings were properly configured.
Mapped those ldap_attr_mappings to some alternative main structural
objectclass oc_map_id and using joins to acuxilary tables leads to
retrieve the info but i am afraid the syntax checks will not be
considered and it leads to not transporting binary information as binary
rather as a hexdump string.
The actual case is person objectClass along with using pkiUser as an
auxiliary objectClass holding the userCertificates and I used the
inetOrgPerson as the alternative main objectClass.
I already checked the odbc settings with test applications and the odbc
driver delivers the db blob object in correct binary mode.
Would somebody comment this and let me know how to force the binary
transfer of those attributess or where is the right place to track that
down why the transfer is done not in binary mode.
Thanks in advance
Babak Nasri
-----------------------------------------------------------------------
Act only in accordance with that maxim through which you can at the same time will that it become a universal law." [Immanuel Kant, Fundamental Principles of the Metaphysic of Morals,1785]