When a user is set inactive in Vokomokum's member system, or when a user is removed from a group, this needs to be picked up by Foodsoft. Currently, these checks are only done at login. So when there is a conflict, it would be helpful if those rules are enforced. Currently the user can keep his priviliges when keeping the session active.
Solution: store timestamp when user info was updated in the session (it's signed thus safe for this), and re-check every x minutes, checked on each request (before_filter in the ApplicationController). It needs to update the workgroups the member is in, as well as logout the user when he's inactive. And while we're at it, also update name and address.
When a user is set inactive in Vokomokum's member system, or when a user is removed from a group, this needs to be picked up by Foodsoft. Currently, these checks are only done at login. So when there is a conflict, it would be helpful if those rules are enforced. Currently the user can keep his priviliges when keeping the session active.
Solution: store timestamp when user info was updated in the session (it's signed thus safe for this), and re-check every x minutes, checked on each request (
before_filter
in theApplicationController
). It needs to update the workgroups the member is in, as well as logout the user when he's inactive. And while we're at it, also update name and address.