[prev in list] [next in list] [prev in thread] [next in thread] 

List:       scout-dev
Subject:    [jira] [Closed] (JUDDI-405) Improve LDAP integration
From:       "Alex O'Ree (JIRA)" <juddi-dev () ws ! apache ! org>
Date:       2013-05-30 23:21:20
Message-ID: JIRA.12468192.1277841816800.44069.1369956080844 () arcas
[Download RAW message or body]


     [ https://issues.apache.org/jira/browse/JUDDI-405?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel \
]

Alex O'Ree closed JUDDI-405.
----------------------------

       Resolution: Fixed
    Fix Version/s: 3.2
         Assignee: Alex O'Ree  (was: Tom Cunningham)
    
> Improve LDAP integration
> ------------------------
> 
> Key: JUDDI-405
> URL: https://issues.apache.org/jira/browse/JUDDI-405
> Project: jUDDI
> Issue Type: Bug
> Affects Versions: 3.1.1
> Reporter: Tom Cunningham
> Assignee: Alex O'Ree
> Fix For: 3.2
> 
> 
> The SimpleLDAPAuthenticator assumes that the SECURITY_PRINCIPAL is the same thing \
> as the Publisher ID, which doesn't make much sense for LDAP.        I think we \
> should extend this a bit so that we get the uid out of LDAP and use that as the \
> default mapping for the publisher ID - I think that makes a lot more sense and \
> allows the user to send whatever bind name they want in for the get_auth_token \
> username. Also, should look at the context connection again and see if we can \
> persist this, although I had a lot of problems trying to get a reconnecting \
> connection to work on OpenLDAP.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


[prev in list] [next in list] [prev in thread] [next in thread]