Interesting approach, I've been thinking about doing something similar
to this, but it didn't seem worth the effort to me. Today would handle
that situation like:
my $sql = select * from view_JobList_Quick WHERE Filter='basic_filter'
$WhereClause;
if ($session-{'UserType') eq 'Publisher')
Hi Nicholas,
I would like to see CAP::Authentication be enhanced to have the ability to
query additional database fields and make the data available to runmodes.
These fields need not be related to authentication. For example, the
ability to specify a user role/privilege field could then avoid
On Thu, Mar 4, 2010 at 5:56 PM, Michael Peters mpet...@plusthree.comwrote:
On 03/04/2010 10:56 AM, Brad Van Sickle wrote:
2) Runmode authorization is a little trickier, but still manageable. I
check the user's session in prerun and if they are not authenticated,
redirect to a not
I'd be very interested in checking that out once it's available. I'm
not sure I like your philosophy of making each module responsible for
it's own security, I like to push as much up to the base class as
possible, but I do love your attention to DB resources.
As someone with a strong
Hi Michael
From Michael Peters mpeters at plusthree.com
On 03/04/2010 10:04 AM, Brad Van Sickle wrote:
Maybe CGI::Application::Dispatch or CAP::Routes is a better/more
powerful way to do this... but I don't see how. Which is why I'm asking.
There are pros and cons to both ways (using
