Repository navigation
Using redis with rubycas-client #8
Description
Activity
I just did something like this but stored the session lookup data in the db not redis. I did it in a way that you should be able to add a redis storage module rather easily. Here is the branch of my fork:
https://github.com/edan/rubycas-client/tree/session_stores
A session store framework has been added the current release. If you would like to add a redis store, I'd be happy to accept a pull request. Please include rspec tests to validate your store works.
I'm thinking of forking and adding in an option to use redis as a datastore for SSO sessions instead of the tmp/sessions directory in Rails. Redis would be a better option for this sort of temporary session, and also simply for the fact that it will work on Heroku much better (given that your app is run by multiple nodes) for Single Sign Out.
is this reasoning sound?