ghenry(a)suretecsystems.com wrote:
> <quote who="ando(a)sys-net.it">
>> ghenry(a)suretecsystems.com wrote:
>>
>>> Just a quick to note that there are some overlays missing from
>>> slapd.overlays.5
>>> in 2.4.4alpha and actual man pages.
>> Please enumerate them; some are intentionally not present because they
>> are not intended for real use.
>
> * dyngroup has no man page, but is listed slapd.overlays.5
> * slapo-valsort.5 isn't in slapd.overlays.5
> * slapo-dds.5 isn't listed in slapd.overlays.5
> * constraint.c has no docs or listed in slapd.overlays.5
slapo-constraint.5 was added to CVS April 29 2006.
> * seqmod.c has no docs or listed in slapd.overlays.5
This is a demo overlay, not intended for actual use.
--
-- Howard Chu
Chief Architect, Symas Corp. http://www.symas.com
Director, Highland Sun http://highlandsun.com/hyc
Chief Architect, OpenLDAP http://www.openldap.org/project/
Tanks for your answer.
I tested by removing the %xxxx% from the URL and the tests are passed; but
there is an error saying that there is no %xxx% token.
I already open a case to the BIND team, but they reply this is not a bind
problem.
However, I will transmit this information to the BIND/DLZ team.
-----Message d'origine-----
De : Pierangelo Masarati [mailto:ando@sys-net.it]
Envoyé : vendredi 23 février 2007 12:56
À : Cyril COUPEL; openldap-its(a)openldap.org
Objet : Re: (ITS#4849) LDAP URL not recognized with bind9
Please keep replies on the Issue Tracking System (ITS) list, otherwise
you'll defeat its purpose of tracking issues.
Cyril COUPEL wrote:
> I agree with this information.
> The fact is the ldapURL is not used as it, the key %zone% (or %client%) is
> replaced with the ns domain (the client name).
>
> It was working well since I upgrade to 2.3.30-r2.
> I tried to downgrade to a previous version of openldap and it was working
> again, so it is a openldap problem.
I see the fact that earlier versions of OpenLDAP were not compliant with
standard track documents as a good reason to improve it by making it
compliant, rather than a reason to keep it broken.
The client is broken since it appears to parse the URL __before__
replacing portions of it that are marked using a character that is
invalid in URLs. Either that client implements and uses its own broken
URL parsing routines (at the risk of parsing broken URLs incorrectly,
since they contain invalid characters), or it does URL parsing __after__
string replacement (i.e. after their string has been turned into a valid
URL).
I don't see why OpenLDAP should break (or, in this case, remain broken)
to maintain compatibility with a poorly implemented client.
p.
Ing. Pierangelo Masarati
OpenLDAP Core Team
SysNet s.n.c.
Via Dossi, 8 - 27100 Pavia - ITALIA
http://www.sys-net.it
------------------------------------------
Office: +39.02.23998309
Mobile: +39.333.4963172
Email: pierangelo.masarati(a)sys-net.it
------------------------------------------
Please keep replies on the Issue Tracking System (ITS) list, otherwise
you'll defeat its purpose of tracking issues.
Cyril COUPEL wrote:
> I agree with this information.
> The fact is the ldapURL is not used as it, the key %zone% (or %client%) is
> replaced with the ns domain (the client name).
>
> It was working well since I upgrade to 2.3.30-r2.
> I tried to downgrade to a previous version of openldap and it was working
> again, so it is a openldap problem.
I see the fact that earlier versions of OpenLDAP were not compliant with
standard track documents as a good reason to improve it by making it
compliant, rather than a reason to keep it broken.
The client is broken since it appears to parse the URL __before__
replacing portions of it that are marked using a character that is
invalid in URLs. Either that client implements and uses its own broken
URL parsing routines (at the risk of parsing broken URLs incorrectly,
since they contain invalid characters), or it does URL parsing __after__
string replacement (i.e. after their string has been turned into a valid
URL).
I don't see why OpenLDAP should break (or, in this case, remain broken)
to maintain compatibility with a poorly implemented client.
p.
Ing. Pierangelo Masarati
OpenLDAP Core Team
SysNet s.n.c.
Via Dossi, 8 - 27100 Pavia - ITALIA
http://www.sys-net.it
------------------------------------------
Office: +39.02.23998309
Mobile: +39.333.4963172
Email: pierangelo.masarati(a)sys-net.it
------------------------------------------
<quote who="ando(a)sys-net.it">
> ghenry(a)suretecsystems.com wrote:
>
>> Just a quick to note that there are some overlays missing from
>> slapd.overlays.5
>> in 2.4.4alpha and actual man pages.
>
> Please enumerate them; some are intentionally not present because they
> are not intended for real use.
* dyngroup has no man page, but is listed slapd.overlays.5
* slapo-valsort.5 isn't in slapd.overlays.5
* slapo-dds.5 isn't listed in slapd.overlays.5
* constraint.c has no docs or listed in slapd.overlays.5
* seqmod.c has no docs or listed in slapd.overlays.5
>
>> Also, relay and rwm are still marked as experimental in some places.
>
>> grep experimental doc/man/man5/*
>>
>> doc/man/man5/slapd-relay.5:This backend and the above mentioned overlay
>> are
>> experimental.
>>
>> doc/man/man5/slapo-rwm.5:This overlay is experimental.
>>
>> I'll help where I can,
>
> Sure. I believe they are no longer experimental, but they still do not
> support back-config, so better wait until they're complete.
>
> p.
>
>
>
> Ing. Pierangelo Masarati
> OpenLDAP Core Team
>
> SysNet s.n.c.
> Via Dossi, 8 - 27100 Pavia - ITALIA
> http://www.sys-net.it
> ------------------------------------------
> Office: +39.02.23998309
> Mobile: +39.333.4963172
> Email: pierangelo.masarati(a)sys-net.it
> ------------------------------------------
>
>
>
cyril_coupel(a)yahoo.fr wrote:
> Full_Name: Cyril COUPEL
> Version: 2.3.30-r2
> OS: Gentoo
> URL: ftp://ftp.openldap.org/incoming/
> Submission from: (NULL) (82.241.40.178)
>
>
> Since the openldap update 2.3.30-r2, le LDAP URL are no more recognized in the
> bind 9.3.4 named.conf.
>
> Reproducible: Always
>
> Steps to Reproduce:
> 1. compile BIND with DLZ and LDAP
> 2. add dlz "ldap zone" {
> database "ldap 2
> v3 simple {} {} {10.1.2.253}
> ldap:///dlzZoneName=%zone%,ou=dns,o=bind-dlz???objectclass=dlzZone
^^^ this is not a valid URL, since the two chars following each "%" are
not a valid pair of hexadecimal digits, as required by URL encoding.
"%" need to be URLescaped, as per RFC3986, section 2.4.
The problem is in the client, not in OpenLDAP software.
p.
Ing. Pierangelo Masarati
OpenLDAP Core Team
SysNet s.n.c.
Via Dossi, 8 - 27100 Pavia - ITALIA
http://www.sys-net.it
------------------------------------------
Office: +39.02.23998309
Mobile: +39.333.4963172
Email: pierangelo.masarati(a)sys-net.it
------------------------------------------
Full_Name: Cyril COUPEL
Version: 2.3.30-r2
OS: Gentoo
URL: ftp://ftp.openldap.org/incoming/
Submission from: (NULL) (82.241.40.178)
Since the openldap update 2.3.30-r2, le LDAP URL are no more recognized in the
bind 9.3.4 named.conf.
Reproducible: Always
Steps to Reproduce:
1. compile BIND with DLZ and LDAP
2. add dlz "ldap zone" {
database "ldap 2
v3 simple {} {} {10.1.2.253}
ldap:///dlzZoneName=%zone%,ou=dns,o=bind-dlz???objectclass=dlzZone
ldap:///dlzHostName=%record%,dlzZoneName=%zone%,ou=dns,o=bind-dlz?dlzTTL,dlzType,dlzPreference,dlzData,dlzIPAddr?sub?(&(objectclass=dlzAbstractRecord)(!(dlzType=soa)))
ldap:///dlzHostName=@,dlzZoneName=%zone%,ou=dns,o=bind-dlz?dlzTTL,dlzType,dlzData,dlzPrimaryNS,dlzAdminEmail,dlzSerial,dlzRefresh,dlzRetry,dlzExpire,dlzMinimum?sub?(&(objectclass=dlzAbstractRecord)(dlzType=soa))
ldap:///dlzZoneName=%zone%,ou=dns,o=bind-dlz?dlzTTL,dlzType,dlzHostName,dlzPreference,dlzData,dlzIPAddr,dlzPrimaryNS,dlzAdminEmail,dlzSerial,dlzRefresh,dlzRetry,dlzExpire,dlzMinimum?sub?(&(objectclass=dlzAbstractRecord)(!(dlzType=soa)))
ldap:///dlzZoneName=%zone%,ou=dns,o=bind-dlz???(&(objectclass=dlzXFR)(dlzIPAddr=%client%))
";
};
to /etc/bind/named.conf
3. start named
Actual Results:
the log says :"failed to parse ldap URL"
Expected Results:
eb 15 16:51:35 sc1 process `named' is using obsolete setsockopt SO_BSDCOMPAT
Feb 15 16:51:35 sc1 named[2220]: Loading 'ldap zone' using driver ldap
Feb 15 16:51:35 sc1 named[2220]: command channel listening on 127.0.0.1#953
Feb 15 16:51:35 sc1 named[2220]: zone 127.in-addr.arpa/IN: loaded serial
2002081601
Feb 15 16:51:35 sc1 named[2220]: zone localhost/IN: loaded serial 2002081601
Feb 15 16:51:35 sc1 named[2220]: running
<quote who="ando(a)sys-net.it">
> ghenry(a)suretecsystems.com wrote:
>
>> Just a quick to note that there are some overlays missing from
>> slapd.overlays.5
>> in 2.4.4alpha and actual man pages.
>
> Please enumerate them; some are intentionally not present because they
> are not intended for real use.
Certainly. Will do in the morning.
>
>> Also, relay and rwm are still marked as experimental in some places.
>
>> grep experimental doc/man/man5/*
>>
>> doc/man/man5/slapd-relay.5:This backend and the above mentioned overlay
>> are
>> experimental.
>>
>> doc/man/man5/slapo-rwm.5:This overlay is experimental.
>>
>> I'll help where I can,
>
> Sure. I believe they are no longer experimental, but they still do not
> support back-config, so better wait until they're complete.
Understood.
>
> p.
>
>
>
> Ing. Pierangelo Masarati
> OpenLDAP Core Team
>
> SysNet s.n.c.
> Via Dossi, 8 - 27100 Pavia - ITALIA
> http://www.sys-net.it
> ------------------------------------------
> Office: +39.02.23998309
> Mobile: +39.333.4963172
> Email: pierangelo.masarati(a)sys-net.it
> ------------------------------------------
>
>
>
kiwi(a)oav.net wrote:
> Full_Name: Xavier Beaudouin
> Version: 2.3.33
> OS: FreeBSD 6.2
> URL: http://www.oav.net/tmp/openldap/
> Submission from: (NULL) (82.225.248.92)
> Sending -> dn : uid=kiwi(a)oav.net,ou=mailboxes,dc=kazar,dc=net
> objectClass : top
> objectClass : kazarPerson
> uid : kiwi(a)oav.net
> cn : Nom Prenom
> description : Sample description
> uidNumber : 10
> gidNumber : 10
> userPassword : Password
> homeDirectory : /home/test
> mailQuota : 50
> CouriermailQuota : 50S
>
> str2entry: entry -1 has no dn
> str2entry(dn) failed
> send_ldap_result: err=0 matched="" text=""
> connection_get(8)
If the above is the way your LDIF is formatted, then back-perl
(actually, str2entry, a helper function in the core of slapd) is working
as intended. There's supposed to be no space between attribute names or
"dn" and the colon ":". Please fix you PERL and report.
p.
Ing. Pierangelo Masarati
OpenLDAP Core Team
SysNet s.n.c.
Via Dossi, 8 - 27100 Pavia - ITALIA
http://www.sys-net.it
------------------------------------------
Office: +39.02.23998309
Mobile: +39.333.4963172
Email: pierangelo.masarati(a)sys-net.it
------------------------------------------