Hallo Alex, I do not understand the question.
Via SOAP the only user that can login is the Admin User. This control user does the necessary operations and SSO. A user that enters then OpenMeetings via the SOAP Gateway gets internally a OpenMeetings account (if the externalUserId was specified in the setUserxxx-Method). But this internal user is disabled and cannot login at the standalone version, it is just needed / good to have the same user-object always associated with the same external user. So I don't think that there is a security issue with webservice users at this point. Sebastian 2010/12/22 AlexG <[email protected]> > Hi all, > > We really need an opportunity to disable current users in > openmeetings(or at least delete them) with webservices exists for now. > Actually we don't care if it would a disable or just setting some > random password/username and resetting them in previous value later, > we just need to prevent some user from login in opemeetings for some > time. > > Will appreciate any ideas. > > -- > 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]<openmeetings-user%[email protected]> > . > For more options, visit this group at > http://groups.google.com/group/openmeetings-user?hl=en. > > -- Sebastian Wagner http://www.webbase-design.de http://openmeetings.googlecode.com http://www.wagner-sebastian.com [email protected] -- 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.
