Hello all,
I've installed openldap 2.4.33 on OpenSUSE 11 and am trying out the perl backend. I got my certificate issues sorted out and everything seems good - until I search our university server which returns dn's such as:
unbCaId=9e3454b178993cc73619606d22c7882755c9cb0d,ou=people,dc=unb,dc=ca
When I return entry from search routine in perl module I get error "str2entry: entry -1 has invalid DN". I can't see anything wrong with the dn (other than it is ugly). Are there length restrictions for individual components of a dn? All similar problems I've discovered on the net are issues with commas, plus signs, quotes or unicode characters. No doubt there is something I've overlooked so please point me in the right direction.
cheers,
Dave C.
Your 2.4.33 install likely doesn't understand the unbCaId attribute and needs the schema for it.
On Wed, Feb 13, 2013 at 05:22:05PM +0000, David Cunningham wrote:
Hello all,
I've installed openldap 2.4.33 on OpenSUSE 11 and am trying out the perl backend. I got my certificate issues sorted out and everything seems good - until I search our university server which returns dn's such as:
unbCaId=9e3454b178993cc73619606d22c7882755c9cb0d,ou=people,dc=unb,dc=ca
When I return entry from search routine in perl module I get error "str2entry: entry -1 has invalid DN". I can't see anything wrong with the dn (other than it is ugly). Are there length restrictions for individual components of a dn? All similar problems I've discovered on the net are issues with commas, plus signs, quotes or unicode characters. No doubt there is something I've overlooked so please point me in the right direction.
cheers,
Dave C.
Hi Dave
----------------------------------------
Hello all,
I've installed openldap 2.4.33 on OpenSUSE 11 and am trying out the perl backend. I got my certificate issues sorted out and everything seems good - until I search our university server which returns dn's such as:
unbCaId=9e3454b178993cc73619606d22c7882755c9cb0d,ou=people,dc=unb,dc=ca
When I return entry from search routine in perl module I get error "str2entry: entry -1 has invalid DN". I can't see anything wrong with the dn (other than it is ugly). Are there length restrictions for individual components of a dn? All similar problems I've discovered on the net are issues with commas, plus signs, quotes or unicode characters. No doubt there is something I've overlooked so please point me in the right direction.
Which program is validating and rejecting the DN?
One possible reason is if the DN validation is insisting that the attribute types in the DN are defined in the schema, so in this case, is the attribute type unbCaId defined?
Chris
openldap-technical@openldap.org
-
Chris Card -
Christopher Wood -
David Cunningham