I’ve had RT2 up and running successfully for a while, and I’m working
on a new implementation based on RT3, and I have a couple of
questions about the new httpd-based mailgate:
The docs state that a user needs to be set up for the mailgate
with permissions to create tickets, but nothing mentions how to
configure the mailgate to use that user. How is that done?
I’m using external authentication for the web UI (we have a custom
apache module that talks to our kerberos server to handle
authentication), but that won’t work for the mailgate. Do I just
need to set up an alternate URL that uses apache basic authentication
to accept mail from the mailgate, or can RT be set to fall back to
internal authentication if the webserver doesn’t authenticate?
Thanks.
Christopher Manly
Unix Systems Administrator
CIT Systems & Operations
Cornell University
706 Rhodes Hall
Ithaca, NY 14853
I’ve had RT2 up and running successfully for a while, and I’m working
on a new implementation based on RT3, and I have a couple of questions
about the new httpd-based mailgate:
my understanding, and I haven’t stared at the mailgate yet, is that it
tries to post to the NoAuth portion of the RT wuib UI.
The docs state that a user needs to be set up for the mailgate with
permissions to create tickets, but nothing mentions how to configure
the mailgate to use that user. How is that done?
dunno, I think it’d be okay if you gave Everybody the rights, not sure
if you want to do that though. Otherwise, ISTR seeing a patch either
on rt-users or rt-devel that would make the mailgate supply a username
and password for for Apache’s Basic Auth.
I’m using external authentication for the web UI (we have a custom
apache module that talks to our kerberos server to handle
authentication), but that won’t work for the mailgate. Do I just need
to set up an alternate URL that uses apache basic authentication to
accept mail from the mailgate, or can RT be set to fall back to
internal authentication if the webserver doesn’t authenticate?
Thanks for the pointers. I’ve got it figured out… comments below.
At 11:40 AM -0800 3/13/03, seph wrote:
I’ve had RT2 up and running successfully for a while, and I’m working
on a new implementation based on RT3, and I have a couple of questions
about the new httpd-based mailgate:
my understanding, and I haven’t stared at the mailgate yet, is that it
tries to post to the NoAuth portion of the RT wuib UI.
Sure enough. Trace the code far enough, and the mailgate talks to
/REST/1.0/NoAuth/mail-gateway.
The docs state that a user needs to be set up for the mailgate with
permissions to create tickets, but nothing mentions how to configure
the mailgate to use that user. How is that done?
dunno, I think it’d be okay if you gave Everybody the rights, not sure
if you want to do that though. Otherwise, ISTR seeing a patch either
on rt-users or rt-devel that would make the mailgate supply a username
and password for for Apache’s Basic Auth.
For now, I’ve decided to just allow access to the aforementioned
mail-gateway script from the local host without authentication.
Christopher Manly
Unix Systems Administrator
CIT Systems & Operations
706 Rhodes Hall
Ithaca, NY 14853