RT doesnt’ authenticate based on IP address. The only time I’ve seen this is
if Apache::Session is handing out cookies of the form AF_SID=’’ which usually
means that it’ can’t write to the sessiondata directoryOn Sat, Jun 30, 2001 at 10:36:38AM +0200, email@example.com wrote:
Yes that’s right with the watcher set all is ok.
Another question regarding authentification :
Authentification, if i got an access to the rt2 with one single IP
(via masquerading) to the internet. If I open another browser (never
connected to RT) in the hidden network, i got the correct authentification
of the other user logged in the internal network. Is it a know issue or
Maybe the session-id is build around the REMOTE IP ?
Can somebody confirm ? if yes I could dig into Mason & Apache::Session ?
On Sat, 30 Jun 2001, Jesse wrote:
I suspect that you want to grant ‘everyone’ the right to ‘see queue’ and ‘create ticket’ and ‘requestor’ the right to ‘show ticket’
On Fri, Jun 29, 2001 at 02:27:30PM +0200, firstname.lastname@example.org wrote:
I have just migrated my old rt queue to rt2 and all is working
perfectly (except some auth issue, it was my fault 8-).It’s really a great
job and a wonderful software.
I have just a question regarding group against a specific queue, i want to
add the possibility for a customer to have the web access to a specific
queue (for multiple customer) and see/update/create his ticket only.
I suspect it’s possible but which option are necessary for this type of
group access to the queue ?
Thanks a lot
rt-users mailing list
jesse reed vincent – email@example.com – firstname.lastname@example.org
70EBAC90: 2A07 FC22 7DB4 42C1 9D71 0108 41A3 3FB3 70EB AC90
autoconf is your friend until it mysteriously stops working, at which
point it is a snarling wolverine attached to your genitals by its teeth
(that said, it’s better than most of the alternatives) – Nathan Mehl