authentication happens too late? Cookie not read?
bouton - September 15, 2009 - 16:16
| Project: | CAS |
| Version: | 5.x-4.x-dev |
| Component: | Code |
| Category: | support request |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | active |
Jump to:
Description
I am new to CAS and SSO.
We have the cas module up and running fine on our site, authenticating against an external CAS server, using it as our SSO.
Works fine/ didn't take too much effort to get to work. Almost...
Scenario:
If a user goes to one of our Cas enabled sites and logs on, then goes to our drupal site, they are not automatically logged on to drupal (ie the link still says login). If then the user clicks the login link, the login message appears and they are logged on without having to fill in the login form again.
Why is the login not happening immediately upon their coming to the page having been 'approved' by CAS elsewhere?
Thanks
#1
You can control this behavior with the :
Check to see if a user is allready logged in?
Option in the cas settings page.
Some folks want to require login to visit a site some want to have the users decide whether to log in, (only log in if I need to make modifications) Some want it the way you do.
#2
I have the "Check to see if a user is already logged in?" option ticked and still have the problem mentioned above. Any other suggestions?
Like I said, it knows the user is logged in because when you click the login button you are immediately logged in. A session not being read when the page is opened maybe?
We have a semi-hacked drupal 5.x system... don't ask I came into it after it was all done. Where would I start to look. template.php? page.tpl?
Thanks!
#3
Yes, try making sure you have trailing slash on your CAS uri field. I had this wierd situation where cas worked without the trailing URI but the check authentication method ddidn't. I'm not sure if this is a bug in phpCAS library or the cas server or what...