You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@continuum.apache.org by Jimmy Conway <ji...@gmail.com> on 2008/09/01 13:56:47 UTC
base.dn in security.properties - why it uses not the full line?
There is a problem with LDAP configuration. I specified these lines in
/conf/security.properties.
ldap.config.base.dn=ou=OrgUnit,dc=<mydomain>,dc=com
ldap.config.mapper.attribute.user.base.dn=ou=OrgUnit,dc=<mydomain>,dc=com
(<mydomain> includes the name of my real domain name)
And this is what I get in continuum.log:
2008-09-01 07:43:22,871 [btpool0-7] INFO ldapController - Searching for
user: guest
2008-09-01 07:43:22,871 [btpool0-7] INFO ldapController - Searching for
users with filter: '(&(objectClass=inetOrgPerson)(uid=guest))' from base dn:
ou=OrgUnit
2008-09-01 07:43:22,932 [btpool0-7] ERROR userManager#ldap - Failed to find
user: guest
Why it cuts out the rest of the base.dn? Why base dn is only "ou=OrgUnit"?
Below in log I see this also:
Caused by: javax.naming.NameNotFoundException: [LDAP: error code 32 - No
Such Object]; remaining name 'ou=OrgUnit'
I'm talking about latest version of Continuum from /trunk.
Thanks in advance!
Jim
__________ Information from ESET NOD32 Antivirus, version of virus signature
database 3403 (20080901) __________
The message was checked by ESET NOD32 Antivirus.
http://www.eset.com
Re: base.dn in security.properties - why it uses not the full line?
Posted by "Carr, Brian M" <br...@austin.utexas.edu>.
There is an error in the redback config (i'm not at my development computer,
so I can't say the exact location of the error) stuff that reads the
user.base.dn as a string instead of a list. As such, only the first part of
the list is read.
Removing the base dn just has redback search the entire directory with
subtree scope. As such, it magically begins working. However, if your
directory contains non-user accounts, you may be allowing accounts in to
continuum that you do not intend.
--b
On 9/1/08 8:18 AM, "Jimmy Conway" <ji...@gmail.com> wrote:
> I found the solution. I just removed this line:
>
> ldap.config.mapper.attribute.user.base.dn
>
> I don't know why, but it works now :)
>
> Jim
>
>
> -----Original Message-----
> From: Jimmy Conway [mailto:jimmycnw@gmail.com]
> Sent: Monday, September 01, 2008 1:57 PM
> To: users@continuum.apache.org
> Subject: base.dn in security.properties - why it uses not the full line?
>
> There is a problem with LDAP configuration. I specified these lines in
> /conf/security.properties.
>
> ldap.config.base.dn=ou=OrgUnit,dc=<mydomain>,dc=com
> ldap.config.mapper.attribute.user.base.dn=ou=OrgUnit,dc=<mydomain>,dc=com
>
> (<mydomain> includes the name of my real domain name)
>
> And this is what I get in continuum.log:
>
> 2008-09-01 07:43:22,871 [btpool0-7] INFO ldapController - Searching for
> user: guest
> 2008-09-01 07:43:22,871 [btpool0-7] INFO ldapController - Searching for
> users with filter: '(&(objectClass=inetOrgPerson)(uid=guest))' from base dn:
> ou=OrgUnit
> 2008-09-01 07:43:22,932 [btpool0-7] ERROR userManager#ldap - Failed to find
> user: guest
>
> Why it cuts out the rest of the base.dn? Why base dn is only "ou=OrgUnit"?
>
> Below in log I see this also:
>
> Caused by: javax.naming.NameNotFoundException: [LDAP: error code 32 - No
> Such Object]; remaining name 'ou=OrgUnit'
>
> I'm talking about latest version of Continuum from /trunk.
>
> Thanks in advance!
>
> Jim
>
>
>
>
> __________ Information from ESET NOD32 Antivirus, version of virus signature
> database 3403 (20080901) __________
>
> The message was checked by ESET NOD32 Antivirus.
>
> http://www.eset.com
>
>
>
> __________ Information from ESET NOD32 Antivirus, version of virus signature
> database 3404 (20080901) __________
>
> The message was checked by ESET NOD32 Antivirus.
>
> http://www.eset.com
>
>
>
> __________ Information from ESET NOD32 Antivirus, version of virus signature
> database 3404 (20080901) __________
>
> The message was checked by ESET NOD32 Antivirus.
>
> http://www.eset.com
>
>
______________________________
Brian M. Carr
Identity and Access Management
ITS Applications
University of Texas at Austin
V: 512-232-6419
F: 512-471-5746
brianmcarr@austin.utexas.edu
RE: base.dn in security.properties - why it uses not the full line?
Posted by Jimmy Conway <ji...@gmail.com>.
I found the solution. I just removed this line:
ldap.config.mapper.attribute.user.base.dn
I don't know why, but it works now :)
Jim
-----Original Message-----
From: Jimmy Conway [mailto:jimmycnw@gmail.com]
Sent: Monday, September 01, 2008 1:57 PM
To: users@continuum.apache.org
Subject: base.dn in security.properties - why it uses not the full line?
There is a problem with LDAP configuration. I specified these lines in
/conf/security.properties.
ldap.config.base.dn=ou=OrgUnit,dc=<mydomain>,dc=com
ldap.config.mapper.attribute.user.base.dn=ou=OrgUnit,dc=<mydomain>,dc=com
(<mydomain> includes the name of my real domain name)
And this is what I get in continuum.log:
2008-09-01 07:43:22,871 [btpool0-7] INFO ldapController - Searching for
user: guest
2008-09-01 07:43:22,871 [btpool0-7] INFO ldapController - Searching for
users with filter: '(&(objectClass=inetOrgPerson)(uid=guest))' from base dn:
ou=OrgUnit
2008-09-01 07:43:22,932 [btpool0-7] ERROR userManager#ldap - Failed to find
user: guest
Why it cuts out the rest of the base.dn? Why base dn is only "ou=OrgUnit"?
Below in log I see this also:
Caused by: javax.naming.NameNotFoundException: [LDAP: error code 32 - No
Such Object]; remaining name 'ou=OrgUnit'
I'm talking about latest version of Continuum from /trunk.
Thanks in advance!
Jim
__________ Information from ESET NOD32 Antivirus, version of virus signature
database 3403 (20080901) __________
The message was checked by ESET NOD32 Antivirus.
http://www.eset.com
__________ Information from ESET NOD32 Antivirus, version of virus signature
database 3404 (20080901) __________
The message was checked by ESET NOD32 Antivirus.
http://www.eset.com
__________ Information from ESET NOD32 Antivirus, version of virus signature
database 3404 (20080901) __________
The message was checked by ESET NOD32 Antivirus.
http://www.eset.com