jeremyhaile/devise_cas_authenticatable — comment on commit 6da6c10b12a9a7a004b92a23f44403ca60154a49
File:  line 0
By dyson:

Got this working but had to hack a bunch of code to get it there.

I'm running:
* devise (2.0.4 4ce7854)
* devise_cas_authenticatable (1.0.0 4f76f73)
* rails (3.2.1)
* rubycas-client (2.3.8 7558814)
* warden (1.1.1)

Most noticeably the session ID wasn't being stored. Once I got it storing it I found Devise creates a new session after successful login and destroys the old on. That's fine but after successful login and redirect, warden never runs any devise code from what I could tell as it determines there is an authenticated session already. This meant the storing of the key never happened again in devise_cas_authenticatable because the cas_session_controller was never called again and the old key was still in the rails cache. I moved the storing of the session key to a before filter in the application controller so now it happens on ever request but it's a hack.

I can provide much more info if you like but as your patch is for 3.1 and I am on 3.2 perhaps when/if you update you will see and be able to fix any issues better than me.

My version is up at https://github.com/dyson/devise_cas_authenticatable/tree/3.1-single-sign-out.