[
https://jira.codehaus.org/browse/MRM-998?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=310010#comment-310010
]
Chris Harris commented on MRM-998:
----------------------------------
I recently wrote to the mailing list about this issue. Had I known about this
particular bug, I would have had an answer to my problem. I'm also forced to
authenticate against Active Directory. I was very confused as to why I
couldn't find the userPassword field as I've seen listed in so many
Redback/LDAP examples. I thought it was because my account, specified by
ldap.config.bind.dn, wasn't an admin account. I was using my AD account for
testing purposes, because that's the only to which I have access.
This really needs to get fixed! This could be a potential deal-breaker for a
lot of people attempting to set up Archiva in an AD environment. That's a lot
of people and companies. Archiva, at this point in time, is really turning
into a superior Maven repo manager. This bug alone deprives you of
strengthening your current user base and delivering your fine product to a
wider audience. Just saying...keep up the good work.
> LDAP configuration isn't flexible enough to use in my env (Active Directory)
> doesnt have a password attribute.
> --------------------------------------------------------------------------------------------------------------
>
> Key: MRM-998
> URL: https://jira.codehaus.org/browse/MRM-998
> Project: Archiva
> Issue Type: Bug
> Components: Users/Security
> Affects Versions: 1.1.3
> Environment: Ubuntu 8.10, x86_64
> Reporter: Andy Brook
> Labels: LDAP
> Fix For: Backlog
>
>
> Hi,
> I would love to enable the ldap stuff, I have all manner of apps using ldap
> (jira,confluence,openfire etc). I cannot use ldap with Archiva as Active
> Directory (not my choice) doesn't store user passwords as an attribute, I
> have to 'connect' with the user credentials in order to verify them.
> Please extend LDAP support to remove the reliance on a password atrribute and
> enable user provided passwords at the login prompt to be used in the ldap
> connection to validate authentication.
> At Archiva startup, it stacks, so is trying to do something tha tit cant.
> {noformat}
> 5422 [WrapperSimpleAppMain] INFO org.quartz.core.QuartzScheduler - Scheduler
> defaultScheduler_$_NON_CLUSTERED started.
> org.codehaus.plexus.redback.common.ldap.connection.LdapException: Could not
> connect to the server. [Root exception is
> javax.naming.AuthenticationException: [LDAP: error code 49 - 80090308:
> LdapErr: DSID-0C090334, comment: AcceptSecurityContext error, data 525, vece]]
> at
> org.codehaus.plexus.redback.common.ldap.connection.LdapConnection.<init>(LdapConnection.java:81)
> at
> org.codehaus.plexus.redback.common.ldap.connection.ConfigurableLdapConnectionFactory.getConnection(ConfigurableLdapConnectionFactory.java:130)
> at
> org.codehaus.plexus.redback.users.ldap.LdapUserManager.newDirContext(LdapUserManager.java:338)
> at
> org.codehaus.plexus.redback.users.ldap.LdapUserManager.findUser(LdapUserManager.java:214)
> {noformat}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
