>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. 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/