Skip Menu |

This queue is for tickets about the Catalyst-Plugin-Authentication CPAN distribution.

Report information
The Basics
Id: 24150
Status: resolved
Priority: 0/
Queue: Catalyst-Plugin-Authentication

People
Owner: Nobody in particular
Requestors: chris+rt [...] chrisdolan.net
Cc:
AdminCc:

Bug Information
Severity: Wishlist
Broken in: 0.08
Fixed in: (no value)



Subject: Per-realm 'use_session' setting
[This report is against v0.10, SVN rev 5946] I'm using authentication with two realms: student and instructor. The latter uses cookies to persist the login, but the former must not (it is a small section of the site and must be functional in a reduced browser environment). To enable this dichotomy, I'm forced to set 'use_session' to false in the authentication config, so I lose the convenience of authentication-controlled sessions. I would prefer that I could control the session per-realm. This could be accomplished most easily by making use_session a per-realm property. A more involved solution would be to add realms to Catalyst::Plugin::Session. -- Chris
From: CDOLAN [...] cpan.org
I've been informed this should be submitted as an RFC to the email list. Fair enough, I'll try to do that. In the meantime, I thought I'd share a workaround: I added the following line of code to the signin() action of my non-cookie controller and it works well enough for now. local $c->config->{authentication}->{use_session} = 0; if (!$c->authenticate(...)) { ... } -- Chris
The just-released version of the module (0.10007) allows resolution of this issue. There are now two possible solutions to this issue: 1) a per-realm use_session config variable. If this is not set, the global use_session config variable will be used. 2) The method of user persistence is now completely controlled by the realm object. (See USER PERSISTENCE in the module docs) This means you can subclass realm and define your own user persistence methods... including none at all. Jay