in reply to Re: RFC: Authentication/Authorization System
in thread RFC: Authentication/Authorization System

Good ideas. I just want to make sure I don't run into the "too many options" problem while trying to get around it. Basicaly I just want a place I can start, and then link to the other modules that do better or have better options. In addition I'm not sure how i'd go about making a program dynamic enough to be able to write to all of those different authentication systems. So I was hoping to make an Authentication/Authorization System in a box, then point people to more powerfull solutions that could be customized to different needs. Does that make more sense? Kinda user managment with training wheels, i'd fully expect people to ditch the training wheels eventualy, but some projects never get off the ground enough to worry about that. At least thats been my experience, which is why i'm meditating on this, to see if i'm alone or if others have similar experiences. ;)


___________
Eric Hodges
  • Comment on Re^2: RFC: Authentication/Authorization System

Replies are listed 'Best First'.
Re^3: RFC: Authentication/Authorization System
by rhesa (Vicar) on Jul 19, 2006 at 20:52 UTC
    I can sympathise with you not wanting to aim too high just yet :)

    The typical solution to talking to different backends is usually by adding a driver layer (similar to the DBD::* modules for DBI). I've been browsing through the source for Authen::Simple, and the basic design looks very good. It uses Adaptor classes which implement the backend-store specific code behind the public, common API. It may be too abstract for your needs, but I think I can recommend it. It's interesting and educational at least :)