Full_Name: Patrick Laimbock
Version: RE24
OS: CentOS 6.3 x86_64
URL: ftp://ftp.openldap.org/incoming/
Submission from: (NULL) (94.210.175.192)
In the OpenLDAP Admin Guide on page 38 it says:
34. olcSuffix: "dc=example,dc=com"
35. olcDbDirectory: /usr/local/var/openldap-data
36. olcRootDN: "cn=Manager,dc=example,dc=com"
37. olcRootPW: secret
38. olcDbIndex: uid pres,eq
39. olcDbIndex: cn,sn,uid pres,eq,approx,sub
When I try to slapadd that example config I get the following errors:
5117a0af str2entry: invalid value for attributeType olcSuffix #0 (syntax
1.3.6.1.4.1.1466.115.121.1.12)
5117a1ea str2entry: invalid value for attributeType olcRootDN #0 (syntax
1.3.6.1.4.1.1466.115.121.1.12)
/etc/openldap34/slapd.d: line 1: duplicate index definition for attr "uid"
When I remove the quotes from the olcSuffix (line 34) and olcRootDN (line 36)
entries and remove the double uid from either line 38 or line 39 then the
slapadd action is successful.
Hi Howard,
Thank you!
I have updated the Debian bug report [1].
Cheers,
Balint
[1]: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=673038
2013/2/7 Howard Chu <hyc(a)symas.com>:
> I've committed an alternate fix for this to git master, filed against
> ITS#6365. Please test and let us know your results, thanks.
> The patch is in commit 853b9d1335d27e280751e9cfb8ca6b5356ffec73
>
> --
> -- Howard Chu
> CTO, Symas Corp. http://www.symas.com
> Director, Highland Sun http://highlandsun.com/hyc/
> Chief Architect, OpenLDAP http://www.openldap.org/project/
I've committed an alternate fix for this to git master, filed against
ITS#6365. Please test and let us know your results, thanks.
The patch is in commit 853b9d1335d27e280751e9cfb8ca6b5356ffec73
--
-- Howard Chu
CTO, Symas Corp. http://www.symas.com
Director, Highland Sun http://highlandsun.com/hyc/
Chief Architect, OpenLDAP http://www.openldap.org/project/
quanah(a)zimbra.com wrote:
> --On Wednesday, February 06, 2013 6:33 PM +0000 TCera(a)sjrwmd.com wrote:
>
>> --_000_EE54DB3B9E0D63489B0845CE62912E8C3BAD846ABY2PRD0511MB441_
>> Content-Type: text/plain; charset="us-ascii"
>> Content-Transfer-Encoding: quoted-printable
>>
>> xwiki uses jldap.
>>
>> http://www.openldap.org/jldap/
>
> JLDAP is written in java, and does not use the OpenLDAP C libraries. If
> you are going to use Java, I highly recommend you look at the unboundID SDK.
>
> I would also note that PHP's LDAP Support is known to be utterly broken.
> There is no indication anywhere here in your report that indicates a bug
> with the OpenLDAP software.
If he could reproduce the issue using OpenLDAP's command line tools, there
would be reason to suspect libldap. But no such problem occurs for me using
e.g. ldapsearch. Closing this ITS.
--
-- Howard Chu
CTO, Symas Corp. http://www.symas.com
Director, Highland Sun http://highlandsun.com/hyc/
Chief Architect, OpenLDAP http://www.openldap.org/project/
--On Wednesday, February 06, 2013 6:33 PM +0000 TCera(a)sjrwmd.com wrote:
> --_000_EE54DB3B9E0D63489B0845CE62912E8C3BAD846ABY2PRD0511MB441_
> Content-Type: text/plain; charset="us-ascii"
> Content-Transfer-Encoding: quoted-printable
>
> xwiki uses jldap.
>
> http://www.openldap.org/jldap/
JLDAP is written in java, and does not use the OpenLDAP C libraries. If
you are going to use Java, I highly recommend you look at the unboundID SDK.
I would also note that PHP's LDAP Support is known to be utterly broken.
There is no indication anywhere here in your report that indicates a bug
with the OpenLDAP software.
--Quanah
--
Quanah Gibson-Mount
Sr. Member of Technical Staff
Zimbra, Inc
A Division of VMware, Inc.
--------------------
Zimbra :: the leader in open source messaging and collaboration
--_000_EE54DB3B9E0D63489B0845CE62912E8C3BAD846ABY2PRD0511MB441_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
xwiki uses jldap.
http://www.openldap.org/jldap/
Without delving deeper, I don't know whether jldap uses openldap libraries =
or not. I thought that it might since it was an openldap project. Though =
if jldap and openldap are different enough then this issue points to a prob=
lem then with Active Directory. On the other hand, Windows login, email, .=
..etc. were unaffected by the comma and period in the password.
Regardless - take the comma and period out of my password, both tikiwiki an=
d xwiki work.
--_000_EE54DB3B9E0D63489B0845CE62912E8C3BAD846ABY2PRD0511MB441_
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:=
//www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
<meta name=3D"Generator" content=3D"Microsoft Word 12 (filtered medium)">
<style>
<!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
span.EmailStyle17
{mso-style-type:personal-compose;
font-family:"Calibri","sans-serif";
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
-->
</style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=3D"EN-US" link=3D"blue" vlink=3D"purple">
<div class=3D"WordSection1">
<p class=3D"MsoNormal">xwiki uses jldap.<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p> </o:p></p>
<p class=3D"MsoNormal">http://www.openldap.org/jldap/<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p> </o:p></p>
<p class=3D"MsoNormal">Without delving deeper, I don't know whether jldap u=
ses openldap libraries or not. I thought that it might since it was a=
n openldap project. Though if jldap and openldap are different enough=
then this issue points to a problem then with
Active Directory. On the other hand, Windows login, email, …et=
c. were unaffected by the comma and period in the password.
<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p> </o:p></p>
<p class=3D"MsoNormal">Regardless - take the comma and period out of my pas=
sword, both tikiwiki and xwiki work.
<o:p></o:p></p>
</div>
</body>
</html>
--_000_EE54DB3B9E0D63489B0845CE62912E8C3BAD846ABY2PRD0511MB441_--
--On Wednesday, February 06, 2013 12:50 PM +0000 tim(a)cerazone.net wrote:
> Full_Name: Tim Cera
> Version: 2.4.23-26.el6_3.2
> OS: CentOS
> URL: ftp://ftp.openldap.org/incoming/
> Submission from: (NULL) (74.252.34.1)
>
>
> Currently using tikiwki (PHP) with LDAP authentication, and began
> experimenting with xwiki (Java) also with LDAP authentication. Both
> against an Active Directory server. With both systems you cannot
> authenticate a password with either a comma or a period, so suspect it is
> the underlying OpenLDAP libraries. The test password had both a comma
> and period, and the account is locked right now so I can't easily test
> which one or both are required to activate the bug.
I would suspect you are incorrect if you are having this problem with a
Java program, since Java would not be linked to the OpenLDAP C libraries.
--Quanah
--
Quanah Gibson-Mount
Sr. Member of Technical Staff
Zimbra, Inc
A Division of VMware, Inc.
--------------------
Zimbra :: the leader in open source messaging and collaboration
Full_Name: Tim Cera
Version: 2.4.23-26.el6_3.2
OS: CentOS
URL: ftp://ftp.openldap.org/incoming/
Submission from: (NULL) (74.252.34.1)
Currently using tikiwki (PHP) with LDAP authentication, and began experimenting
with xwiki (Java) also with LDAP authentication. Both against an Active
Directory server. With both systems you cannot authenticate a password with
either a comma or a period, so suspect it is the underlying OpenLDAP libraries.
The test password had both a comma and period, and the account is locked right
now so I can't easily test which one or both are required to activate the bug.
I did try looking for this bug suspecting that it would have been reported, and
didn't find it. Hope this isn't a duplicate.
Please find the patch at:
https://dl.dropbox.com/u/94235048/back_ldap_omit_unknown_schema.patch
The attached file is derived from OpenLDAP Software. By virtue of my employment agreement with Symas Corporation, I have assigned my rights and interest to Symas Corporation. Symas Corporation has not assigned rights and/or interest to any party. I, Ted C. Cheng, am authorized by Symas Corporation, my employer, to release this work under the following terms.
Symas Corporation hereby place the following modifications to OpenLDAP Software (and only these modifications) into the public domain. Hence, these modifications may be freely used and/or redistributed for any purpose with or without attribution and/or other notice.
Ted C. Cheng
Symas Corporation
Full_Name: Ted C. Cheng
Version: HEAD
OS: Linux/Solaris
URL: ftp://ftp.openldap.org/incoming/
Submission from: (NULL) (76.174.253.197)
This patch allows back-ldap to ignore unknown schema defined by a remote
(foreign) LDAP server. Clients do not need to handle schema that are not local
to the slapd server.