Changes between Version 2 and Version 3 of FeatureRequests/SecurityFeatures

Timestamp:

04.08.2011 00:29:45 (13 years ago)

Author:

JuergeN

Comment:

--

FeatureRequests/SecurityFeatures

@@ -1 +1 @@
 == Implement User, Role, ACL, Security Concept ==
 
-{{{
-DeepaMehta needs an enhaced permission control system.
-}}}
+
+DeepaMehta needs an enhaced permission control system (PCS). Security needs to be implemented at the server back end and all access must be authenticated, e.g. through tokens. The client-server communication should be secured by TLS/SSL. For the special needs in the context of DeepaMehta we cannot apply strict ACL or OCL lists. Due to the nature of DeepMehta a combined ACL and OCL approach in regard of the workspaces must be implemented into the PCS. 
 
 === User Concept ===
 
 Every operation in DeepaMehta should be done by an identified user. Users (and groups) should be handled through UID (and GID)
-
 
 {{{
@@ -55 +53 @@
 Roles should be assined to users and groups.
 
-
 === Attributes ===
 Every object should have a set of inherent attributes ( which may be properties or associations), e.g.