Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Single sign out doesn't destroy session #75

Closed
cthielen opened this issue Mar 11, 2014 · 3 comments
Closed

Single sign out doesn't destroy session #75

cthielen opened this issue Mar 11, 2014 · 3 comments

Comments

@cthielen
Copy link

Is there something special to do so that single sign out destroys the session hash? I've written support for single sign out into my application and can confirm it's being handled by my application in the logs but it doesn't seem to destroy the user's associated session hash.

Is it supposed to? How does one check that a CAS session has been expired via the single sign out?

@cthielen
Copy link
Author

I think what's actually going on here is that under Rails 4, you have to use the activerecord-session_store gem, which apparently moved session_class to ActionDispatch::Session::ActiveRecordStore.

@cthielen
Copy link
Author

I figured this out. It has to due with Rails 4 compatibility. Please see the open pull request.

@tydaniel
Copy link

I want to apply Rubycas-client with Bitnami Redmine.
But Single sign out doesn't work.
I just did all of steps according to README.
Error Log shows;

NoMethodError (undefined method session_class' for ActiveRecord::SessionStore:Module): lib/redmine/sudo_mode.rb:63:in sudo_mode'

I don't know how to set the session class into redmine.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants