[Date Prev][Date Next]
2.2 & update capacity for SSO
I would like to use an OL 2.2 server with bdb backend to provide
session persistence (single sign-on) between different web
applications that already share the LDAP server (and only have that in
The idea would be to update a session attribute every time a user logs
in and store uid & session id in the cookie sent to the browser.
Can OL handle this kind of load? Let's say, 5 logins/second?
Off-topic question: even if OL can handle the load, would it be bad
form to use it this way?