Re: [smartweb-devel] Requirements for auth module

[rlogiacco <rlo...@us...>]

amarini wrote:
>=20
> My idea on the management of the authorizations is that the structure mus=
t
> be the much simple one, easy performing and understanding but at the same
> time useful, highly flexible and untied from the platform.
>=20
We share the same vision :-)


amarini wrote:
>=20
> A user, assimilating to others, can approach something, often leaked and
> can manage it to a defined level: user, group, role, property, permission=
.=20
> All without subordination of an entity to one another: a user can be in
> relation to one or more groups but can also be free and vice versa; both
> can have one or more roles to which grant permissions in order to manage
> the access to the functionalities (where to navigate, what to visualize,
> how to interact) and both can have property in order to manage the tracin=
g
> of the data (which geographic, economic, temporal contents=E2=80=A6).
>=20
Actually you depicted 90% of the smartweb auth module, but you added
something: a new perspective to the problem which I would better
investigate.

I think you are proposing to resolve the scope and function problems with a
standard parameters map through which associate properties to roles and
users... It could be a simple solution to the big problem: what about
helping us to analyze the idea? I think a little bit of documentation can
help: an ER or class diagram should do the trick to clarify the idea.

I think applying the AOP paradigm to the Jakarta Struts Taglib we can easil=
y
use the properties map to simplify the JSP development... more I think abou=
t
it and more I like your suggestion!

Can you provide a diagram of some sort?
--=20
View this message in context: http://www.nabble.com/Requirements-for-auth-m=
odule-tf3513039s17546.html#a11259530
Sent from the SmartWeb Developers mailing list archive at Nabble.com.