* On Thu, Mar 19 2009, Adam Witney wrote:
> Hi Bill,
>
> This is using PostgreSQL. The other apps are fat clients that can pull
> data from external sources, it was therefore necessary to have the
> security levels built into the database.
Actually, there is really no reason to rely on the databas
Hi,
I have implemented such an authentication sheme. I'm rather new to catalyst
so I do not pretend it si the best way.
Anyway what I've done is :
1) add the session and authentication plugins to catalyst app:
use Catalyst qw/...
Authentication
Session
Session::Store::FastMmap
Session:State::Coo
>
>
> Actually, there is really no reason to rely on the database for this.
I absolutely disagree. There's an authentication mechanism already
implemented in SGBD so why on earth not use it.
Moreover if you want to benefit for logging features of SGBD like Oracle,
your users have to be logged us
Karl Forner wrote:
2) write a custom Authentication plugin, the your specific code is in
_authenticate_against_SGDB
package Serono::Gecko::Business::CredentialVerifier;
use Catalyst::Plugin::Authentication::User::Hash;
sub authenticate {
my ( $self, $c, $realm, $authinfo ) = @_;
You kn
I've found that URI parameters (?foo=bar) function fine but unicode
characters in Chain() arguments do not survive from one page to the
next.
Specifically, this does not work for a chain involving captured
unicode based arguments:
$uri = $c->uri_for(
$c->controller($controller)->action_for($a
On 21 Mar 2009, at 00:02, Rod Taylor wrote:
I've found that URI parameters (?foo=bar) function fine but unicode
characters in Chain() arguments do not survive from one page to the
next.
This is almost certainly a bug.
Can you try and work up a test case, either against C::P::U, or
against
