[
https://issues.apache.org/jira/browse/OPENMEETINGS-593?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13623305#comment-13623305
]
Robert Murdock commented on OPENMEETINGS-593:
---------------------------------------------
Resolved. Apparently when you have duplicate email addresses the user cannot
login. I removed the duplicate address and all users logged in successfully.
> 2.1 AD integration
> ------------------
>
> Key: OPENMEETINGS-593
> URL: https://issues.apache.org/jira/browse/OPENMEETINGS-593
> Project: Openmeetings
> Issue Type: Bug
> Components: BuildsAndReleases
> Affects Versions: 2.1.0 Apache Release
> Reporter: Robert Murdock
> Assignee: SebastianWagner
> Priority: Minor
>
> tried several configuration attempts with OM 2.1 with no success. I cannot
> login with my AD credentials. OM 2.0 works fine. i know there are new
> commands in 2.1 ldap.cfg file. here is my .cfg file
> #specify the LDAP Server type
> ldap_server_type=AD
> #LDAP URL
> ldap_conn_url=ldap://dc1.gsc.local:389
> #Login distinguished name (DN) for Authentification on LDAP Server - keep
> emtpy if not requiered
> ldap_admin_dn=myadmin
> #Loginpass for Authentification on LDAP Server - keep emtpy if not requiered
> ldap_passwd=mypass
> #base to search for userdata(of user, that wants to login)
> ldap_search_base=dc:NETWORK,dc:Local
> # Fieldnames (can differ between Ldap servers)
> field_user_principal=userPrincipalName
> # Ldap auth type(SIMPLE,NONE)
> ldap_auth_type=SIMPLE
> # Ldap ignore upper/lower case, convert all input to lower case
> ldap_use_lower_case=false
> # Ldap-password synchronization to OM DB
> ldap_sync_password_to_om=no
> # optional
> # the timezone has to mach an entry in the OpenMeetings table "omtimezones"
> otherwise the user
> will get
> # the timezone defined in the value of the conf_key "default.timezone" in
> OpenMeetings
> "configurations" table
> #ldap_user_timezone=timezone
> # optional, only absolute URLs make sense
> #ldap_user_picture_uri=picture_uri
--
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
