|
From: JP P. <jp....@ti...> - 2003-05-26 20:21:15
|
Hi Brett, I don't have for now the need of instance authorization, but it is well understandable. AOP would be a nice choice as the authorizations could be done in the beans definition files without puzzling the code. It is really an "aspect". Jean-Pierre > -----Message d'origine----- > De=A0: spr...@li... > [mailto:spr...@li...] De la part > de Brett Bell > Envoy=E9=A0: lundi 26 mai 2003 11:44 > =C0=A0: spr...@li... > Objet=A0: Re: [Springframework-developer] Authentication >=20 > Hi >=20 > Unfortunately, JAAS only supports class based Authorisation(i.e. a user > can operate on a particular type) where a number of business cases require > instance based security (i.e. can this user operate on this specific > instance). I have written a framework recently to support instance based > authorisation at work so I can write a new one for Spring if that's ok, > possibly sprucing it up to use AOP. >=20 > Please let me know what you think. >=20 > Cheers >=20 >=20 > Brett >=20 >=20 >=20 >=20 > ------------------------------------------------------- > This SF.net email is sponsored by: ObjectStore. > If flattening out C++ or Java code to make your application fit in a > relational database is painful, don't do it! Check out ObjectStore. > Now part of Progress Software. http://www.objectstore.net/sourceforge > _______________________________________________ > Springframework-developer mailing list > Spr...@li... > https://lists.sourceforge.net/lists/listinfo/springframework-developer |