Re: [Catalyst] Catalyst with HTTP authentication
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 ::Remote. Everything has its pros and cons. If you do all your authentication in your app, you depend on existing modules for the desired authentication method, or you have to write your own authentication code. I prefer using stable and tested mechanisms over writing my own code (if possible). And if a tool lacks some features which I need, I just use something else (again, if possible). I guess 90% of all webservers support most common authentication methods. Until now, I used DBIC based authentication within my app, and ::Remote for everything else. But until now "everything else" is just one project which requires digest, certificates and kerberos authentication. I guess there is no "better" in this case. Its a matter of personal preferences and use case. Concerning the differing code for testing and production: I agree. This truly is a disadvantage when using ::Remote cheers, Lukas ___ 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@lists.scsys.co.uk/ Dev site: http://dev.catalyst.perl.org/
Re: [Catalyst] Catalyst with HTTP authentication
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 authentication method and storage which is supported by your >>> webserver, including htpasswd files. >> >> How do you pass the remote user in a reverse proxy? >> >> > > It's just http headers, it'll just transparently pass through the proxy. > > (Unless you mean you want to do the authentication on the proxy, rather than > the app servers). I want to do the latter. ___ 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@lists.scsys.co.uk/ Dev site: http://dev.catalyst.perl.org/
Re: [Catalyst] Catalyst with HTTP authentication
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 supported by your >> webserver, including htpasswd files. > > How do you pass the remote user in a reverse proxy? > > It's just http headers, it'll just transparently pass through the proxy. (Unless you mean you want to do the authentication on the proxy, rather than the app servers). Cheers t0m ___ 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@lists.scsys.co.uk/ Dev site: http://dev.catalyst.perl.org/
Re: [Catalyst] Is there an authentication store for htdigest files?
On 12 Mar 2013, at 14:13, Robert Rothenberg wrote: > I am using Catalyst::Authentication::Credential::HTTP and would like to use > digest authentication with htdigest files. > > Is there an htdigest equivalent of Catalyst::Authentication::Store::Htpasswd? Not afaik I'm afraid. Cheers t0m ___ 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@lists.scsys.co.uk/ Dev site: http://dev.catalyst.perl.org/
[Catalyst] Is there an authentication store for htdigest files?
I am using Catalyst::Authentication::Credential::HTTP and would like to use digest authentication with htdigest files. Is there an htdigest equivalent of Catalyst::Authentication::Store::Htpasswd? ___ 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@lists.scsys.co.uk/ Dev site: http://dev.catalyst.perl.org/
Re: [Catalyst] Catalyst with HTTP authentication
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 you pass the remote user in a reverse proxy? ___ 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@lists.scsys.co.uk/ Dev site: http://dev.catalyst.perl.org/
Re: [Catalyst] Catalyst with HTTP authentication
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 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. 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 ::Remote. > > I am using Catalyst::Authentication::Credential::Testing for > authentication when the webserver is not available (when running the > catalyst test-server during development). > > Maybe this is an option for you... > > cheers, Lukas > > On 03/11/2013 03:10 PM, Robert Rothenberg wrote: >> 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::Authentication::Store::Htpasswd, but it does not work >> with Catalyst::Authentication::Credential::HTTP. >> >> I'm not clear on how to do this, without having to write my own handlers for >> HTTP authentication. >> >> >> ___ >> 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@lists.scsys.co.uk/ >> Dev site: http://dev.catalyst.perl.org/ > > ___ > 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@lists.scsys.co.uk/ > Dev site: http://dev.catalyst.perl.org/ *"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"* T-Systems Austria GesmbH Rennweg 97-99, 1030 Wien Handelsgericht Wien, FN 79340b *"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"* Notice: This e-mail contains information that is confidential and may be privileged. If you are not the intended recipient, please notify the sender and then delete this e-mail immediately. *"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"* ___ 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@lists.scsys.co.uk/ Dev site: http://dev.catalyst.perl.org/
Re: [Catalyst] Catalyst with HTTP authentication
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@lists.scsys.co.uk/ Dev site: http://dev.catalyst.perl.org/
