Loading...
 
Skip to main content

Architecture / Installation


Single Sign On with HTTP Authentication

I'm trying to host multiple applications, and provide a single sign on for all users. That is, they sign onto my application, and they get into tikiwiki with the same username, without having to type username/password again.

I found some great information here:
http://tikiwiki.org/tiki-index.php?page=HttpAuthenticationAdminQuestion

I'm not actually using Http Authentication though. Instead, I'm using a mod_perl handler in my apache server to manage my login and sessions. When a valid user is logged in, I call

Image
Copy to clipboard
$r->user($username)

Where $r is my Apache::Request. The net effect of this is that it appears to tikiwiki as if Http Authentication had been used. And, it works! Which makes me very happy, but I would not be writing if there weren't a catch.

The problem is later I log the user out, but tikiwiki still has them logged in. This is NOT the problem with Http Authentication where browsers never forget the users identity. Rather, it is because tikiwiki is storing the user in the PHP session, which is associated with a cookie I don't have control over, as far as I can tell.

I've tried unsetting $r->user. I've tried setting it to an invalid user name. Tikiwiki pays no attention and the user remains logged in.

I'm willing to go into the php and make whatever changes are necessary. Can anyone suggest the best fix?

Thanks,

-Dave