RE: [Tikiwiki-devel] Login Bug

[LIMBURG, M. <mar...@ba...>]

Howdy,

 >>> session_set_cookie_params(0,$tikiname);
 >>> 
 >>> to a file included by every page (for example: tiki-setup.php).
 >>> 
 >>> ($tikiname is your www.domain.tld/$tikiname/)

 >> Shouldn't this be a tiki option? I think it's safe to say I will not 
 >> be the only one with this problem, so how about adding it to tiki 
 >> itself?

 > Sure, my suggestion was just a quick hack so you could use it. I am 
 > not a developer of Tiki (yet ;)

 >> (consider this a feature request :) )

 > Actual solution could be different for Tiki. For example, you could
 > still have one PHPSESSID, but different session variables, like 
 > "user-$tikione" and "user-$tikitwo" instead of just one common "user". 
 > I think developers should think which one is "The Right Way". (Is this 
 > list a place for developers' discussions?)

Indeed, when I worked with the Geeklog project, we ended up providing a
default cookie name, and allow the admin to alter those details.  This way,
if running two or more webapps under the same domain provided a 'seperate'
session state.  Allowing the admin to alter those details was more a
debugging feature than providing a 'smooth' solution.  You need a unified
A&A (access and authorisation) model for this, and a single cookie across
sites is only one step to produce this.

Mark