continuum :: redback :: security.properties not overriding properly application.xml

Details

  • Type: Bug Bug
  • Status: Closed Closed
  • Priority: Major Major
  • Resolution: Duplicate
  • Affects Version/s: 1.2.2
  • Fix Version/s: None
  • Component/s: None
  • Labels:
    None
  • Environment:
    apache-tomcat-6.0.18
    Maven version: 2.0.9
    Java version: 1.6.0_03
    OS name: "linux" version: "2.6.18-6-amd64" arch: "amd64" Family: "unix"
  • Complexity:
    Intermediate

Description

in webapps/continuum/WEB-INF/classes/META-INF/plexus/application.xml I 'hardcoded' my user.base.dn as ou=People,dc=jquantlib,dc=org, as shown below:

<component>
<role>org.codehaus.plexus.redback.common.ldap.UserMapper</role>
<role-hint>ldap</role-hint>
<implementation>org.codehaus.plexus.redback.common.ldap.LdapUserMapper</implementation>
<configuration>
<email-attribute>email</email-attribute>
<full-name-attribute>givenName</full-name-attribute>
<password-attribute>userPassword</password-attribute>
<user-id-attribute>cn</user-id-attribute>
<user-base-dn>ou=People,dc=jquantlib,dc=org</user-base-dn>
<user-object-class>inetOrgPerson</user-object-class>
</configuration>
<requirements>
<requirement>
<role>org.codehaus.plexus.redback.configuration.UserConfiguration</role>
</requirement>
</requirements>
</component>

I was obliged to do it in this file and repackage the .WAR file because the value specified is not properly loaded.
For instance, if I defined

user.manager.impl=ldap
ldap.bind.authenticator.enabled=true
redback.default.admin=admin
redback.default.guest=guest
security.policy.password.expiration.enabled=false
user.manager.impl=cached
ldap.bind.authenticator.enabled=true

ldap.config.hostname=localhost
ldap.config.port=389
ldap.config.base.dn=dc=jquantlib,dc=org
ldap.config.context.factory=com.sun.jndi.ldap.LdapCtxFactory
ldap.config.bind.dn=cn=admin,dc=jquantlib,dc=org
ldap.config.password=secret
#ldap.config.authentication.method=

ldap.config.mapper.attribute.email=mail
ldap.config.mapper.attribute.fullname=givenName
ldap.config.mapper.attribute.password=userPassword
ldap.config.mapper.attribute.user.id=cn
#ldap.config.mapper.attribute.user.base.dn=ou=People,dc=jquantlib,dc=org
ldap.config.mapper.attribute.user.object.class=inetOrgPerson
#ldap.config.mapper.attribute.user.filter=

As a matter of test, I changed user.base.dn as show below:
ldap.config.mapper.attribute.user.base.dn=ou=Test,dc=jquantlib,dc=org

In continnum.log it shows like this:
INFO ldapController - Searching for users with filter: '(&(objectClass=inetOrgPerson)(cn=guest))' from base dn: ou=Test

If I comment out that line...
#ldap.config.mapper.attribute.user.base.dn=ou=Test,dc=jquantlib,dc=org

it show like this in the logfile:
INFO ldapController - Searching for users with filter: '(&(objectClass=inetOrgPerson)(cn=guest))' from base dn: ou=People,dc=jquantlib,dc=org

It means that "ou=Test,dc=jquantlib,dc=org" was wrongly read as "ou=Test"

Thanks

Richard Gomes
http://www.jquantlib.org/index.php/User:RichardGomes

Issue Links

is superceded by

Task - A task that needs to be done. CONTINUUM-2116 Upgrade to Redback 1.2 release

  • Blocker - Blocks development and/or testing work, production could not run
  • Closed - The issue is considered finished, the resolution is correct. Issues which are not closed can be reopened.
relates to

Bug - A problem which impairs or prevents the functions of the product. REDBACK-168 LDAP filters with comma in them does not work

  • Major - Major loss of function.
  • Closed - The issue is considered finished, the resolution is correct. Issues which are not closed can be reopened.

Activity

Ascending order - Click to sort in descending order
Hide
Permalink
Patric Lichtsteiner added a comment -

Same issue with 1.2.3

Show
Patric Lichtsteiner added a comment - Same issue with 1.2.3
Hide
Permalink
Brett Porter added a comment -

fixed in 1.3.2 in the linked issues

Show
Brett Porter added a comment - fixed in 1.3.2 in the linked issues
Hide
Permalink
Tim Pinet added a comment -

I am still seeing this issue in v1.3.6 but it was only occurring for the ldap email property. In security.properties I set

ldap.config.mapper.attribute.user.email=mail

But in application.xml the attribute was

<email-attribute>email</email-attribute>

I was confused as to why the user list was not populating E-mail addresses. I eventually changed application.xml to

<email-attribute>mail</email-attribute>

and now the user list displays email addresses. I still think that this one field in security.properties is not overriding application.xml properly.

Show
Tim Pinet added a comment - I am still seeing this issue in v1.3.6 but it was only occurring for the ldap email property. In security.properties I set ldap.config.mapper.attribute.user.email=mail But in application.xml the attribute was <email-attribute>email</email-attribute> I was confused as to why the user list was not populating E-mail addresses. I eventually changed application.xml to <email-attribute>mail</email-attribute> and now the user list displays email addresses. I still think that this one field in security.properties is not overriding application.xml properly.

People

  • Assignee:
    Brett Porter
    Reporter:
    Richard Gomes
Vote (1)
Watch (3)

Dates

  • Created:
    Updated:
    Resolved: