SSO tries to access the already delete session

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Ensure SSO is truned on in the server
2. Login to App, then logout 
3. Session/ticket mapping gets cleared by the logout action. Then Cas
server calls back for single signout which looks for session/ticket mapping
again & throws 

Errno::ENOENT (No such file or directory -
tmp/sessions/cas_sess.ST-1216311988rF7826314FD027E1158):

/projects/cas-demo/vendor/plugins/rubycas-client/lib/casclient/frameworks/rails/
filter.rb:243:in
`read'

/projects/cas-demo/vendor/plugins/rubycas-client/lib/casclient/frameworks/rails/
filter.rb:243:in
`read_service_session_lookup'

/projects/cas-demo/vendor/plugins/rubycas-client/lib/casclient/frameworks/rails/
filter.rb:175:in
`single_sign_out'

/projects/cas-demo/vendor/plugins/rubycas-client/lib/casclient/frameworks/rails/
filter.rb:18:in
`filter'

Original issue reported on code.google.com by thiy...@gmail.com on 17 Jul 2008 at 4:49

[GoogleCodeExporter]

I am not 100% on this but do you have a tmp/sessions directory in your Rails
application? If not try to make one and give it write perms 777 (see note ** 
below). 

I believe I had this problem on start up because my Rails app was owned by
user=wmernagh and rails runs as user=apache. apache did not have permission to 
create
the tmp/sessions directory.

** For security reasons you will have to change the perms from 777 to 755 and 
give
apache access to it. The above is just a quick fix to test this out.

Original comment by wmern...@gmail.com on 12 Sep 2008 at 2:20

[GoogleCodeExporter]

Original comment by matt.zuk...@gmail.com on 23 Sep 2008 at 5:42

• Changed state: Accepted

[GoogleCodeExporter]

Fixed as of rev 171

Original comment by matt.zuk...@gmail.com on 1 Oct 2008 at 7:01

• Changed state: Fixed