Now that rt-mailgate uses a webpage to submit tickets, $WebExternalAuth
gets in the way. I’m not sure if a --user and --pass option should be
added to rt-mailgate or if just a note in the install documentation would
be enough.
In my case, I’m going override CurrentUser::IsPassword to do the external
checking and remove $WebExternalAuth.
-james
Now that rt-mailgate uses a webpage to submit tickets, $WebExternalAuth
gets in the way. I’m not sure if a --user and --pass option should be
added to rt-mailgate or if just a note in the install documentation would
be enough.
If you haven’t configured your web server to let requests to the various
NoAuth directories, I suspect that this won’t be the only thing that
bites you. But yes, I’d take a patch to let the mailgate do HTTP auth
when necessary.
In my case, I’m going override CurrentUser::IsPassword to do the external
checking and remove $WebExternalAuth.-james
rt-devel mailing list
rt-devel@lists.fsck.com
http://lists.fsck.com/mailman/listinfo/rt-devel
»|« Request Tracker... So much more than a help desk — Best Practical Solutions – Trouble Ticketing. Free.