OK, I found this error. My ldap.cfg was wrong. This is how it should
look:

#ConfigurationFile for LDAP Auth

#specify the LDAP Server type
ldap_server_type=ActiveDirectory

#LDAP URL
ldap_conn_url=ldap://192.168.0.6:389

#Login distinguished name (DN) for Authentification on LDAP Server -
keep emtpy if not requiered
ldap_admin_dn=CN:Administrator,CN:Users,DC:out-put,DC:net
#Loginpass for Authentification on LDAP Server - keep emtpy if not
requiered
ldap_passwd=root12

#base to search for userdata(of user, that wants to login
ldap_search_base=dc:out-put,dc:net
# Fieldnames (can differ between Ldap servers)
field_user_principal=userPrincipalName


# Ldap auth type(SIMPLE,NONE)
ldap_auth_type=SIMPLE


Now I've got another Problem: It Basically works. I can login with
user: [email protected] (userPrincipalName from ADS )

But every First Time a user logs in - I get the Question about in
which Organisation I want to be. But the Box, where I could choose is
empty! But I am sure, there are Organisations created. When I click on
OK - I just get the upper Part of the Openmeetings Application
(Profile, Logout, Report a Bug). Then I log out.

When I am Login in then - it works! Now Problems anymore!

But what can I do to have this working without these Problems in the
Beginning?

Another Question:

Ist it somehow possible to Login with the sAMAccountName? I mean if it
is possible to use a Setting like this:

field_user_principal=sAMAccountName

or something similar...

Best Regards
Markus

On 21 Mai, 16:47, Markus <[email protected]> wrote:
> Hello,
>
> I am having Problems with the Active Directory Authentification with
> Openmeetings.
>
> Everytime, I try to login I get this Error in the red5 error.log :
>
> 2010-05-21 16:44:56,299 [NioProcessor-1] ERROR
> o.o.app.data.user.Usermanagement -
>
> Authentification on LDAP Server failed : [LDAP: error code 49 -
> 80090308: LdapErr: DSID-0C090334, comment: AcceptSecurityContext
> error, data 525, vece]
>
> This is my ldap.cfg:
>
> #ConfigurationFile for LDAP Auth
> #ConfigKey 'ldap_config_path' must be set in DataBase Configration of
> OM and point to this file
> #o.becherer,14.01.2009
>
> #specify the LDAP Server type
> ldap_server_type=ActiveDirectory
>
> #LDAP URL
> ldap_conn_url=ldap://192.168.0.6:389
>
> #Login distinguished name (DN) for Authentification on LDAP Server -
> keep emtpy if not requiered
> ldap_admin_dn=CN:ADMINISTRATOR,CN:USERS,DC:OUT-PUT,DC:NET
>
> #Loginpass for Authentification on LDAP Server - keep emtpy if not
> requiered
> ldap_passwd=secret
>
> #base to search for userdata(of user, that wants to login
> ldap_search_base=CN:USERS,DC:OUT-PUT,DC:NET
>
> # Fieldnames (can differ between Ldap servers)
> field_user_principal=sAMAccountName
>
> # Ldap auth type(SIMPLE,NONE)
> ldap_auth_type=SIMPLE
>
> my openmeetings.log:
>
>  WARN 05-21 16:46:19.561 MainService.java 5747417 254
> org.openmeetings.app.remote.MainService [NioProcessor-1] - loginUser
> 111: fb8fbc3ab794274c772e7c940b49624f michaela
> DEBUG 05-21 16:46:19.562 Usermanagement.java 5747418 1384
> org.openmeetings.app.data.user.Usermanagement [NioProcessor-1] -
> Usermanagement.getUserByLoginOrEmail : michaela
> DEBUG 05-21 16:46:19.563 MainService.java 5747419 271
> org.openmeetings.app.remote.MainService [NioProcessor-1] - Ldap Login
>
> The User I am trying to Authenticate is "michaela".
>
> I hope, someone can Help me.
>
> Thanks in Advance,
> Markus
>
> --
> You received this message because you are subscribed to the Google Groups 
> "OpenMeetings User" group.
> To post to this group, send email to [email protected].
> To unsubscribe from this group, send email to 
> [email protected].
> For more options, visit this group 
> athttp://groups.google.com/group/openmeetings-user?hl=en.

-- 
You received this message because you are subscribed to the Google Groups 
"OpenMeetings User" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to 
[email protected].
For more options, visit this group at 
http://groups.google.com/group/openmeetings-user?hl=en.

Reply via email to