I rolled my own based on a couple of blog articles I found about role-
based authorization in Rails -

http://metautonomo.us/2008/09/30/easy-role-based-authorization/
http://blog.gugl.org/archives/41

May or may not be more useful than what you've already tried.

Mark.


On Aug 8, 8:36 pm, Christian Hoeppner <[email protected]> wrote:
> I would expect whatever I'd plug in to provide me with means to define
> and check for permits, in different contexts, like operator specific
> (does this operator has this role or permit?), or depending on another
> object (is this operator the owner of this object?).
>
> Of course, you have a very valid point, but a framework like this would
> severely cut down on boilerplate code, don't you think?
>
> El sáb, 08-08-2009 a las 18:19 -0700, Jon Hancock escribió:
>
> > What are your requirements?  Authorization tends to be very app
> > specific.  How do you see a framework/plugin helping you better than
> > incrementally adding authorization behavior to your User or Roles
> > objects?
>
> > Jon
>
> > On Aug 7, 10:39 pm, Christian Hoeppner <[email protected]>
> > wrote:
> > > Hey
>
> > > So, I need some authorization for my app. I've been cooking around with
> > > some self-built role-based approach, but it's quickly getting out of
> > > comtrol. I will have to dedicate some extra time to this. But for now...
> > > is there any plugin, piece of code, etc... that I could use?
>
> > > A quick google dug up nothing too interesting. I found two plugins, one
> > > of which is deemed as "sucks" by the author, and the other one looks
> > > like a weekend job, and that's about as much as I found.
>
> > > Any hints are greatly apreciated.
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"merb" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [email protected]
For more options, visit this group at http://groups.google.com/group/merb?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to