Le 19/05/2010 11:21, t.lem...@gmail.com a écrit :
Hi Sebastian,
Le 19/05/2010 09:35, Sebastian Wagner a écrit :
hm,
I read your problem about not beeing able to set the UserDN in the
field ExternalUser_Id because the field is a numeric type.
And about the *ExternalUserType* but I do not see any comment about a
new field required or referenced "auth-type" in the user-object.
Sorry, I meant ExternalUserType, not a new "auth-type" field... I mixed
this with another project I'm working on.
Where did you write that down?
In ticket 1208:
http://code.google.com/p/openmeetings/issues/detail?can=2&q=1208&colspec=ID%20Modified%20Type%20Status%20Stars%20Component%20Priority%20Milestone%20Owner%20Summary&id=1208
Comment 4 (t.lemeur Apr 15, 2010)
[QUOTE]Applying this patch means that the Users table in OM DB must be
updated so
that Usersthat were previously added with LDAP import have their
ExternalUserType
field updated to "LDAP"
[/QUOTE]
Note that if you forget to fix this, your users will still be able to
login, but as
if they were locally defined (no more Synch with LDAP data).
Then Comment 5 (t.lemeur May 11, 2010)
About my comment #4,
the simplest way to update an om system after this fix is applied is
to use the
following algorithm:
IF (LDAP-Authentication enabled)
THEN
FOREACH non-admin-users
DO
Update the user entry by setting the EXTERNAL_USER_TYPE_LDAP DB
field to "LDAP"
DONE
END IF
I'm not sure where in the code is the "update DB" method used during
updgrade.
Thibault
--
You received this message because you are subscribed to the Google Groups
"OpenMeetings User" group.
To post to this group, send email to openmeetings-u...@googlegroups.com.
To unsubscribe from this group, send email to
openmeetings-user+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/openmeetings-user?hl=en.
