I am not forced to use Spring Security. The only reason why we have
chosen it is based on previous projects that worked fine with Spring
Security. So moving to another framework is not a problem but we want
to reuse existing knowledge and code, as much as possible. Thanks for
the tip! Will look into Shiro.
2012/2/18 Felipe Carvalho <
[hidden email]>:
> Hi, Marco, as far as I could understand from spring security, it does not
> support the concept of permissions.
>
> If its not mandatory for you to use spring security, you may want to try
> shiro plugin. Shiro is a security framework from Apache, I've been using it
> for 2 years now, works fine and fits your need.
>
> On Feb 18, 2012 11:27 AM, "Marco Pas" <
[hidden email]> wrote:
>>
>> Hi there,
>>
>> in our current application the concept of a user Role is a bit to
>> limited. We need a more finer grained way of identifying permissions.
>>
>> Example:
>>
>> User has a Role 'OPERATOR' but we need different kind of 'OPERATORS'
>> with settings like:
>> isAllowedToCreateUsers
>> isAllowedToCreateA
>> isAllowedToCreateB
>> ...
>>
>>
>> Any idea on how to tackle/model this?
>>
>> ---------------------------------------------------------------------
>> To unsubscribe from this list, please visit:
>>
>>
http://xircles.codehaus.org/manage_email>>
>>
>
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email