Re: [Trinidad] Authorisation & Authentication? (JAAS?)

Yes, Acegi will be the right solution with Spring. I've used it in an JSF-Spring application and it's very powerful, not so hard to integrate btw. On the other hand, for securing ui components you may take a look at myfaces securitycontext features. http://wiki.apache.org/myfaces/SecurityContext

Re: [Trinidad] Authorisation & Authentication? (JAAS?)

If you're already in the Spring game, Acegi seems a reasonable incremental solution. -- Adam On 7/10/07, Shane Petroff <[EMAIL PROTECTED]> wrote: Frank Nimphius wrote: Usually authorization is enforced on the business service layer and surfaces in the UI. If e.g. a user has a permission, J

Re: [Trinidad] Authorisation & Authentication? (JAAS?)

Frank Nimphius wrote: Usually authorization is enforced on the business service layer and surfaces in the UI. If e.g. a user has a permission, JAAS or container managed, to update an attribute then this could/should be exposed in the UI through expression language, referencing a method on the

Re: [Trinidad] Authorisation & Authentication? (JAAS?)

Darren, Trinidad is a component set and does not have a security infrastructure. You can use the render property or the readOnly property to perform authorization, but this needs to be backed up somewhere. Usually authorization is enforced on the business service layer and surfaces in the UI. If

[Trinidad] Authorisation & Authentication? (JAAS?)

Hi all, Can anyone please point me in the right direction as regards methods to execute authorisation & authentication to a Trinidad webapp. Something along the lines of Java Authentication and Authorization Service (JAAS ). We want to implement an authori