Garry,
In our testing, this works fine. Perhaps you have the old version stuck in your Mason cache?
Garry,
In our testing, this works fine. Perhaps you have the
old version stuck in your Mason cache?
Hi Jesse
Ive purged the cache and still have the issue.
Ive got a feeling its to do with the way we’re doing PAM authentication, as
the logs are showing a PAM auth failure, followed by an attempt to login
locally which works.
the access log shows Im attempting to get the ticket id
[23/Nov/2010:10:30:12 +0000] “GET /Ticket/Display?id=103131 HTTP/1.1” 301
340 “-” “Mozilla/5.0 (Linux; U; Android 2.2; en-gb; HTC Desire 2.10.161.2
Build/FRF91) AppleWebKit/533.1 (KHTML, like Gecko) Version/4.0 Mobile
Safari/533.1”
And the messages log shows the PAM failure
Nov 23 10:30:35 telos RT: User me failed PAM authentication
(/opt/rt3/bin/…/local/lib/RT/CurrentUser.pm:345)
Nov 23 10:30:35 telos RT: User me falling back to RT database authentication
(/opt/rt3/bin/…/local/lib/RT/CurrentUser.pm:349)
Nov 23 10:30:35 telos RT: Successful login for me from 158.125.226.123
(/opt/rt3/bin/…/lib/RT/Interface/Web.pm:430)
Then I just get the index page, so my guess is the fallback scrubs the url
somehow.
Ill try to fix the PAM issue and see if that sorts it all.
Thanks for getting back.
Garry
Dr Garry Booth
IT Services
Loughborough University