LDAP (Active Directory) login - AcceptSecurityContext error

[GoogleCodeExporter]

OpenMeetings rev.3247 (svn trunk)

When configured for LDAP login with UserID (usually used for logging into
windows), simple bind authenticates it against displayName, not
sAMAccountName or CN. (See
http://www.winserverkb.com/Uwe/Forum.aspx/windows-server-ad/32747/LDAP-Simple-Bi
nd-with-trusted-domain-user-credentials#201022520456davidthomassuncorpcomau)

If login is different from displayName, users are getting
AcceptSecurityContext error

I created a patch, which first searches for distinguishedName and then uses
it for authentication against AD, so displayName can have different value
than login.

I am not java programmer at all, so it is just a quick patch, which seems
to work well.

Original issue reported on code.google.com by jakub.ka...@dek-cz.com on 3 Jun 2010 at 11:20

Attachments:

• openmeetings_patch.diff

[GoogleCodeExporter]

hi
Are there any update about this issue? we have the same problem in version 1.5
thanks

Original comment by hinojos...@gmail.com on 21 Dec 2010 at 3:08

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

However, a good idea to add support for ldap AD.
You can indicate the approximate date of adding the patch, or that his reply 
and will not be in this application.

Original comment by alon...@gmail.com on 31 Jan 2011 at 12:39

[GoogleCodeExporter]

Original comment by seba.wag...@gmail.com on 31 Jan 2012 at 12:23

• Added labels: Restrict-AddIssueComment-Commit

[GoogleCodeExporter]

OpenMeetings moves to Apache Foundation, update your bookmarks to the new 
project page:

http://incubator.apache.org/openmeetings/

New Issue tracker is located: https://issues.apache.org/jira/browse/OPENMEETINGS

New Mailing Lists located at: 
http://incubator.apache.org/openmeetings/mail-lists.html 

Original comment by seba.wag...@gmail.com on 31 Jan 2012 at 12:25