Hello,
we decided to run our rt2-Installation on a https-server to protect the
password exchange.
I successfully migrated rt2 to rt3 now, but couldn’t configure the
mailgate, because since version 3 it need another parameter --url <URL for
RT’s web interface>.
But mailgate does not support “https” and all messages bounce with
An Error Occurred
501 Protocol scheme ‘https’ is not supported
how to go with this? Can something be configured or do we need to wait
until mailgate supports https?
Thanks,
Dirk Pape.
Hello Steve,
–Am Donnerstag, 27. März 2003 11:25 Uhr -0500 schrieb Steve Neruda
steve_neruda@neruda.com:
I wound up configuring https but allowing localhost to use http. I had
to work around a MSIE bug to keep from getting frequent errors when
posting. Finally I use mod-rewrite to parse out the email address to use
a a userid.
thank you, serving http to localhost works well.
I now use external auth on the external https and disabled
“PerlAuthenHandler Apache::AuthPAM” on the localhost http.
What do you mean by the second hint?
Does rt-mailgate authenticate with the email-adress?
Regards,
Dirk.
Hello Steve
–Am Donnerstag, 27. März 2003 13:08 Uhr -0500 schrieb Steve Neruda
steve_neruda@neruda.com:
Not a very good userid to most systems. The modrewrite hack changes
REMOTEUSER to their email address. Does that answer your question?
Yes, thank you. When we start using client certificate, I hopefully will
remember your tip.
Dirk.
Hello,
we decided to run our rt2-Installation on a https-server to protect
the password exchange.
I successfully migrated rt2 to rt3 now, but couldn’t configure the
mailgate, because since version 3 it need another parameter --url <URL
for RT’s web interface>.
But mailgate does not support “https” and all messages bounce with
An Error Occurred
501 Protocol scheme ‘https’ is not supported
You have to install Net::SSLeay so LWP learns about ssl connections.
Regards,
Harald
Harald Wagener * FCB/Wilkens * An der Alster 42 * 20099 Hamburg