[ 
https://jira.duraspace.org/browse/DS-1267?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=26257#comment-26257
 ] 

Ivan Masár commented on DS-1267:
--------------------------------

Hi kgunn,

you should really have started this discussionon dspace-tech before we 
determine whether this really is a bug.

As far as I can see, the significant change here is that you changed the search 
filter from
(&(ldap_id_field=netid))
to
(&(objectClass=user)(ldap_id_field=netid))

The only explanation I can draw from that is thaty there's more than one object 
where ldap_id_field=netid, and of those, the one with objectClass=user should 
be used for authentication. Can you confirm that by posting search results of 
those 2 searches using a tool like ldapsearch? (of course replace netid for a 
real value)

You're right that LDAPAuthenticationHierarchical is currently missing a config 
option for filter and it should be added (3.).

It shouldn't be necessary to run trim() on ldap_search_context, ConfigManager 
already should have done this for you.

I'm not familiar with 1. and 2., but I'll look up what they're for.

I don't see why 4. would be necessary.
                
> Is Active Directory supported by the LDAPAuthentication method in DSpace 1.8.2
> ------------------------------------------------------------------------------
>
>                 Key: DS-1267
>                 URL: https://jira.duraspace.org/browse/DS-1267
>             Project: DSpace
>          Issue Type: Documentation
>          Components: DSpace API
>    Affects Versions: 1.8.2
>         Environment: Active Directory, DSPace
>            Reporter: kgunn
>
> I read DS-50 but was unable to get at the patch. As this issue was raised 
> sometime ago, does DSpace 1.8.2 support authentication against Active 
> Directory using the LDAP Authentication method?
> If so what are the configuration parameters set to as an example?
> Other software like tomcat realms now support AD but allow uuid to be a 
> search filter like (sAMAccountName={0}). I can't get it to work by just 
> setting id_field to sAMAccountName AD attribute.

--
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

------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
Dspace-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/dspace-devel

Reply via email to