On 25 Mar 2013, at 11:54, Robert Rothenberg wrote:
>
> I'd suggest updating the documentation for A::C::Remote accordingly. (I can
> do this if you point me in the direction of the git repo)
git://git.shadowcat.co.uk/catagits/Catalyst-Plugin-Authentication.git
is the read only repository U
On 25/03/13 14:08 Tomas Doran wrote:
>
> On 22 Mar 2013, at 13:34, Robert Rothenberg wrote:
>> I'm unsure what to do here. Should I write a Plack::Middleware plugin that
>> translates the X-Proxy-REMOTE_USER header to an env->{REMOTE_USER}?
>
>
> That's exactly what's needed here :)
Ok. After
On 22 Mar 2013, at 13:34, Robert Rothenberg wrote:
> I'm unsure what to do here. Should I write a Plack::Middleware plugin that
> translates the X-Proxy-REMOTE_USER header to an env->{REMOTE_USER}?
That's exactly what's needed here :)
Cheers
t0m
__
On 22/03/13 11:46 Robert Rothenberg wrote:
> I understand how to have an Apache reverse proxy send the REMOTE_USER as a
> header, with something like
>
> RequestHeader set X-Proxy-REMOTE-USER %{REMOTE_USER}
>
> but how to I get Authentication::Credential::Remote to use the header
> instead of
On 14/03/13 08:51 Tomas Doran wrote:
>
> On 12 Mar 2013, at 17:10, Robert Rothenberg wrote:
>
>>> (Unless you mean you want to do the authentication on the proxy,
>>> rather than the app servers).
>>
>> I want to do the latter.
>
> You should still be able to use Authentication::Credential::Re
On 14/03/13 08:51 Tomas Doran wrote:
>
> On 12 Mar 2013, at 17:10, Robert Rothenberg wrote:
>
>>> (Unless you mean you want to do the authentication on the proxy, rather
>>> than the app servers).
>>
>> I want to do the latter.
>
> You should still be able to use Authentication::Credential::Re
On 12 Mar 2013, at 17:10, Robert Rothenberg wrote:
>> (Unless you mean you want to do the authentication on the proxy, rather than
>> the app servers).
>
> I want to do the latter.
You should still be able to use Authentication::Credential::Remote, you'll just
need to re-configure your web s
On 03/12/2013 01:07 PM, Alexander Hartmaier wrote:
> Having the webserver do the authentication means you are depending on it
> to support the type of authentication you want to use.
> I'd prefer having the authentication in the app with the exact same code
> for production and testing over ::Remo
On 12/03/13 15:36 Tomas Doran wrote:
>
> On 12 Mar 2013, at 13:20, Robert Rothenberg wrote:
>
>> On 11/03/13 15:37 Lukas Thiemeier wrote:
>>
>>> I am using Catalyst::Authentication::Credential::Remote in a current
>>> project. It lets the webserver do all the authentication. You can use
>>> any
On 12 Mar 2013, at 13:20, Robert Rothenberg wrote:
> On 11/03/13 15:37 Lukas Thiemeier wrote:
>
>> I am using Catalyst::Authentication::Credential::Remote in a current
>> project. It lets the webserver do all the authentication. You can use
>> any authentication method and storage which is supp
On 11/03/13 15:37 Lukas Thiemeier wrote:
> I am using Catalyst::Authentication::Credential::Remote in a current
> project. It lets the webserver do all the authentication. You can use
> any authentication method and storage which is supported by your
> webserver, including htpasswd files.
How do
On 2013-03-11 16:37, Lukas Thiemeier wrote:
> >From reading the docs, I don't see why
> Catalyst::Authentication::Store::Htpasswd and
> Catalyst::Authentication::Credential::HTTP do not work together, but I
> have not used any of them.
>
> I am using Catalyst::Authentication::Credential::Remote in
Thanks. That worked, but I'll take a look at
Catalyst::Authentication::Credential::Remote
___
List: Catalyst@lists.scsys.co.uk
Listinfo: http://lists.scsys.co.uk/cgi-bin/mailman/listinfo/catalyst
Searchable archive: http://www.mail-archive.com/catalyst@l
I realized that you don't even have to set password_field correctly.
Something was going terribly wrong in my head, sorry for that.
Only "password_type" has to be set to "self_check", but this is documented.
This means that there is no tricky part at all. Just configure both
modules as described i
Hi,
I just had some time to try it: C::Authentication::Credential::HTTP and
C::Authentication::Store::Htpasswd work together just fine. Here is my
setup:
in TestApp.pm:
use Catalyst qw/
ConfigLoader
Authentication
/;
__PACKAGE__->config(
"Plugin::Authentication" => {
realms => {
Ditto. I am also using Catalyst::Authentication::Credential::Remote, and
it is working just fine.
-Tim
On Mon, Mar 11, 2013 at 9:37 AM, Lukas Thiemeier
wrote:
> >From reading the docs, I don't see why
> Catalyst::Authentication::Store::Htpasswd and
> Catalyst::Authentication::Credential::HTTP
>From reading the docs, I don't see why
Catalyst::Authentication::Store::Htpasswd and
Catalyst::Authentication::Credential::HTTP do not work together, but I
have not used any of them.
I am using Catalyst::Authentication::Credential::Remote in a current
project. It lets the webserver do all the aut
On 11 Mar 2013, at 14:10, Robert Rothenberg wrote:
> There is Catalyst::Authentication::Store::Htpasswd, but it does not work
> with Catalyst::Authentication::Credential::HTTP.
Why? How?
Cheers
t0m
___
List: Catalyst@lists.scsys.co.uk
Listinfo: http
I have a project that requires using HTTP authentication.
There is a Catalyst::Authentication::Credential::HTTP module, but from the
documentation, it does not seem to support using htpasswd files, which I
need, because a separate web site will be using that file.
There is Catalyst::Authenticatio
19 matches
Mail list logo
