You indeed should have a deeper look into PEAR::LiveUser. It's a bit complicated and not very well documented, but Google will show some good tutorials.
Best of luck with your plugin, cheers! Pierre On Aug 19, 1:30 pm, Nicolas CHARLOT <[EMAIL PROTECTED]> wrote: > Hi all, > > Since we often need to manage credentials at a resource level, we're > actually studying about a new security plugin: isicsACLPlugin. > > With sfGuardPlugin, it's easy to manage permissions for a collection > of resources. But what about restricting access to a sub-collection of > resources or even to a particular one ? For instance, if you want to > restrict the view to all the news, a credential news_view is well > enough. But if you want to restrict the same operation to the news of > category 2 or directly to the news 53 ? That's the main purpose of > isicsACLPlugin. > > Another goal is to add a new customization level for end-users. With > Symfony basic security system, it's the developer that tells if an > action is secured or not (security.yml config file). > With isicsACLPlugin, the end-user will be able to define directly if > an operation on resource is: > - public > - restricted to any authenticated user > - or fine-grained secured > > isicsACLplugin is an open source project (LGPL). We hope it will > become a community project and that many apps will use it. > > We've starded to write the specifications here > :http://code.google.com/p/isicsaclplugin/wiki/specsEn > . > If U're interested in contribute or just give your opinion, the door > is open! > > Thanks. > -- > Nicolas CHARLOThttp://www.isics.fr --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "symfony users" 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/symfony-users?hl=en -~----------~----~----~----~------~----~------~--~---
