Re: [smartweb-devel] Requirements for auth module

[amarini <ann...@gm...>]

On purpose of authorizations=E2=80=A6
My idea on the management of the authorizations is that the structure must
be the much simple one, easy performing and understanding but at the same
time useful, highly flexible and untied from the platform.=20
For this reason, the entities I think to, reflect the greater problems but
at the same time the most common reality.=20
A user, assimilating to others, can approach something, often leaked and ca=
n
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 ca=
n
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 tracing of the
data (which geographic, economic, temporal contents=E2=80=A6).

Annamaria
--=20
View this message in context: http://www.nabble.com/Requirements-for-auth-m=
odule-tf3513039s17546.html#a11257671
Sent from the SmartWeb Developers mailing list archive at Nabble.com.