I didn’t realise I could use Apache Auth for RT. That should probably
do the job. I can’t find any details on how to configure this. Any
There are docs and mailing posts all over the place. “external auth”
They may be all over the place, but they’re in places I can’t find.
Searching the wiki for external auth, for example, gives an unanswered
question from someone else wanting to know about this!
Searching for ExternalAuth gives a page that references
’LookupExternalUserInfo’ and ‘WebExternalAuth’ - both of which point to
pages that don’t exist yet.
I saw the “ask questions here” page in the wiki, and was going to answer this
very question in that page, but then later on I noticed that page said to
quit using it, as it wasn’t useful. hrmm…
Here is how I have used this for one install: (On Debian, the package
request-tracker3.2 is what I am using along with the packages apache-perl and
Redirect / https://rt.domain.com/rt32/
AuthName "RT Authentication"
In /etc/request-tracker3.2/RT_SiteConfig.pm :
Set($WebExternalAuth , 1);
Set($WebExternalAuto , 1);
This allows me to authenticate against the local shadow stuffs. The only
problem is that you cannot “logout” of RT. I end up opening another
(non-konqueror) browser, and logging into the https website as root:rootpass
to be able to admin the RT instance. I could set my main user as a
superuser, but I haven’t done that yet.