[ 
https://issues.apache.org/jira/browse/OPENMEETINGS-1492?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15624516#comment-15624516
 ] 

nikolay commented on OPENMEETINGS-1492:
---------------------------------------

I have to create a local LDAP server..For what?
We have already MS AD and don't need one more LDAP..
The output of command SELECT:
id      type    damain_id       login           deleted+0
1       user    (NULL)          admin           0
2       ldap    1               yakovlev_nd     1       
3       ldap    1               vks             1
4       ldap    1               yakovlev_nd     1
5       ldap    1               vks             0
6       ldap    1               vks             0
7       ldap    1               vks             0

Three records with id's 2-4 were deleted via the administrative interface of OM 
some time ago.

Yes, the LDAP configuration uses the parameter "Add Domain to user name" as 
"krvostok.ru".
I will remind that search of the user in MS AD is carried out correctly that 
can't be told about search in local base.

> OM 3.1.3 duplication records in database
> ----------------------------------------
>
>                 Key: OPENMEETINGS-1492
>                 URL: https://issues.apache.org/jira/browse/OPENMEETINGS-1492
>             Project: Openmeetings
>          Issue Type: New Feature
>          Components: LDAP
>    Affects Versions: 3.1.3
>         Environment: OS Centos 7 
>            Reporter: nikolay
>            Assignee: Maxim Solodovnik
>
> I've installed OM 3.1.3 on Centos 7 and I got some ussues.
> The first of them is a dupplication of user's records in a local MySQL DB.
> Each time when a user logs into OM via ldap (MS AD) the new record for this 
> user appears in OM database.
> If a user logs into OM locally (local DB [internal]) then it's OK.
> om_ldap.cfg file has  ldap_provisioning=AUTOCREATE.
> Can anybody help me?
> Thanks.
> Regards 
> Nikolay



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to