Re^2: Passing Data Back From Mason template

Hmmm... don't like embedding roles in URLS -- we often need to change who can do what, create new roles, etc -- would be mess if necessitated remapping urls.

so basically each action (method) in the controller needs a role-list, and jumps off to confirm current user is a member of at least one allowed role, else redirects off to a not-enough-access-to-do-that page, yes?

Comment on Re^2: Passing Data Back From Mason template

Replies are listed 'Best First'.
Re^3: Passing Data Back From Mason template by Joost (Canon) on Jun 04, 2006 at 23:46 UTC
The url mapping isn't going to be useful to you then :-) Yes, I would suggest mapping role-lists against actions. If you do that in the database or whatever storage system you use, or use a consisten interface in your action classes, you can still do a generic access control system after request to action mapping and before dispatching to the action. "What should it profit a man, if he should win a flame war, yet lose his cool?"	[reply]

Replies are listed 'Best First'.

Re^3: Passing Data Back From Mason template
by Joost (Canon) on Jun 04, 2006 at 23:46 UTC

Yes, I would suggest mapping role-lists against actions. If you do that in the database or whatever storage system you use, or use a consisten interface in your action classes, you can still do a generic access control system after request to action mapping and before dispatching to the action.

"What should it profit a man, if he should win a flame war, yet lose his cool?"

[reply]