[
https://issues.apache.org/jira/browse/OPENMEETINGS-1492?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15601534#comment-15601534
]
nikolay commented on OPENMEETINGS-1492:
---------------------------------------
I have executed one experiment.
I changed the ldap_provisionig parameter in the om_ldap.cfg from value
AUTOCREATE to AUTOUPDATE.
Each time when I connected as existing user the enter into OM was blocked and
the message was appeared in the loggs: "User not found in OM DB and
Provisionning.AUTOCREATE was not set".
As the existing user isn't in the database (actually it's not so), an entry in
the database is added.
It was necessary to answer a question: why search of the user existing in the
database doesn't work correctly.
DEBUG 10-24 12:47:48.269 o.a.o.d.d.s.LdapConfigDao:87
[http-nio-0.0.0.0-5080-exec-3] - getActiveLdapConfigs
DEBUG 10-24 12:48:00.032 o.a.o.c.l.LdapLoginManagement:168
[http-nio-0.0.0.0-5080-exec-1] - LdapLoginmanagement.doLdapLogin
WARN 10-24 12:48:00.128 o.a.o.c.l.LdapLoginManagement:210
[http-nio-0.0.0.0-5080-exec-1] - Referral LDAP entry found, ignore it
WARN 10-24 12:48:00.129 o.a.o.c.l.LdapLoginManagement:210
[http-nio-0.0.0.0-5080-exec-1] - Referral LDAP entry found, ignore it
WARN 10-24 12:48:00.130 o.a.o.c.l.LdapLoginManagement:210
[http-nio-0.0.0.0-5080-exec-1] - Referral LDAP entry found, ignore it
ERROR 10-24 12:48:00.186 o.a.o.c.l.LdapLoginManagement:234
[http-nio-0.0.0.0-5080-exec-1] - User not found in OM DB and
Provisionning.AUTOCREATE was not set
DEBUG 10-24 12:48:07.588 o.a.o.c.l.LdapLoginManagement:168
[http-nio-0.0.0.0-5080-exec-8] - LdapLoginmanagement.doLdapLogin
WARN 10-24 12:48:07.692 o.a.o.c.l.LdapLoginManagement:210
[http-nio-0.0.0.0-5080-exec-8] - Referral LDAP entry found, ignore it
WARN 10-24 12:48:07.693 o.a.o.c.l.LdapLoginManagement:210
[http-nio-0.0.0.0-5080-exec-8] - Referral LDAP entry found, ignore it
WARN 10-24 12:48:07.693 o.a.o.c.l.LdapLoginManagement:210
[http-nio-0.0.0.0-5080-exec-8] - Referral LDAP entry found, ignore it
ERROR 10-24 12:48:07.721 o.a.o.c.l.LdapLoginManagement:234
[http-nio-0.0.0.0-5080-exec-8] - User not found in OM DB and
Provisionning.AUTOCREATE was not set
DEBUG 10-24 12:48:25.019 o.a.o.c.l.LdapLoginManagement:168
[http-nio-0.0.0.0-5080-exec-3] - LdapLoginmanagement.doLdapLogin
WARN 10-24 12:48:25.116 o.a.o.c.l.LdapLoginManagement:210
[http-nio-0.0.0.0-5080-exec-3] - Referral LDAP entry found, ignore it
WARN 10-24 12:48:25.117 o.a.o.c.l.LdapLoginManagement:210
[http-nio-0.0.0.0-5080-exec-3] - Referral LDAP entry found, ignore it
WARN 10-24 12:48:25.118 o.a.o.c.l.LdapLoginManagement:210
[http-nio-0.0.0.0-5080-exec-3] - Referral LDAP entry found, ignore it
ERROR 10-24 12:48:25.135 o.a.o.c.l.LdapLoginManagement:234
[http-nio-0.0.0.0-5080-exec-3] - User not found in OM DB and
Provisionning.AUTOCREATE was not set
> 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)
