This works similar to a Cookie, there is a "flash Cookie" called "shared object" this contains a HASH value on the client side. The server side stores the client side HASH associated with the user-id so the server side can auth the user. If the user ticks "remember me" the server will persist the session (meaning the scheduler will not delete the session). Next time the user connects to the server, he will try to auth using his HASH from the FlashCookie. If the server does remember the HASH he will login the user without showing the login window.
This process is quite similar to any Session-Based auth process from any website. Sebastian 2011/10/21 Dmitry Sigaev <[email protected]> > Hello Sebastian, > > In the user authorization in openmeetings there is an option to put a > mark against the field “remember me”. > > Where does the information about the user that put this mark stored? > So he can enter the system from his PC without putting in his login > and pw again. -- Sebastian Wagner http://www.openmeetings.de http://www.webbase-design.de 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.
