From: Kurt D. Z. <Ku...@Op...> - 2001-03-29 14:53:14
|
BTW, the "+" I-D is available at: http://search.ietf.org/internet-drafts/draft-zeilenga-ldapv3bis-opattrs-05.txt comments are welcomed. (likely best privately or on the LDAPext list). Kurt At 06:41 AM 3/29/01 -0800, Kurt D. Zeilenga wrote: >At 12:38 PM 3/29/01 +0100, Chris Ridd wrote: >>> I am trying to access an OpenLDAP 2 server with Net::LDAP. Everything fine >>> so far. But when I try to read schema information via the >>> Net::LDAP::schema method it fails. The reason is that the server does not >>> answers operational attributes such as "subschemaentry". Currently I >>> fixed it by explicitly requesting the operational attributes via attrs => >>> ['+', '*'] in both Net::LDAP::root_dse and Net::LDAP::schema. >> >>As far as I know the '+' character is not part of any RFC-defined way of >>requesting all operational attributes. (There is no RFC-defined way of >>doing this. Again, AFAIK.) > >Yes, '+' as a means for requesting is only a 'work in progress'. >And even when it is published as a RFC, I'd question it's >appropriate for read select operational attributes types. The >'+' mechanisms is more suited to browsing by humans. An >automated application should know what's it after and request >it directly. > >Kurt |