(I failed to include the mailing list in the reponse - bringing it back
to the list)
*From:*Mads Kiilerich [mailto:[email protected]]
*Sent:* Friday, January 23, 2015 1:33 PM
*To:* John Tran
*Subject:* Re: authentication by container or reverse-proxy
On 01/23/2015 08:34 PM, John Tran wrote:
I need to be able to authenticate to Kallithea by sending it a url
such as http://user:[email protected] , which I believe fits the
description of container based or by reverse proxy.
Note that I’m using Kallithea on Windows. I’ve followed the
directions outlined here
https://pythonhosted.org/Kallithea/setup.html for proxy-pass
reverse using Apache (installed on windows). Even though I
enable the proxy pass and location block so that it uses an
.htaccess file, I get two layers of authentication instead of just
one. I get the apache authentication which I can bypass using
http://user:[email protected], yet Kallithea still asks for its
own username and password in the Kallithea gui screen.
Can you describe / show which changes you have done in the
authentication dialog to enable container auth?
Can you somehow verify that Kallithea see REMOTE_USER being set
correctly in the wsgi environment?
(perhaps by enabling debugging and and/or causing a crash where it
will log the full environment)
/Mads
On 01/23/2015 10:35 PM, John Tran wrote:
>
> Mads, I probably should’ve been more clear I’m not sure I really did
use “container auth” as I’m not fully familiar with the term. I only
tried the reverse-proxy method with Apache as the front end.
Yeah, you have to enable the authentication plugin at the /_admin/auth
url. Please help improving the documentation if it fails to explain it
sufficiently clear.
/Mads
_______________________________________________
kallithea-general mailing list
[email protected]
http://lists.sfconservancy.org/mailman/listinfo/kallithea-general
