pracro:acl
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
pracro:acl [2011/04/11 12:02] – deva | pracro:acl [2011/04/13 14:33] (current) – deva | ||
---|---|---|---|
Line 1: | Line 1: | ||
======ACL====== | ======ACL====== | ||
- | =====Design1===== | + | =====Server===== |
+ | ====Design1==== | ||
Templates contain ACLs. The users and roles are defined in a config file.\\ | Templates contain ACLs. The users and roles are defined in a config file.\\ | ||
Template: | Template: | ||
Line 33: | Line 34: | ||
</ | </ | ||
- | =====Design2===== | + | ====Design2==== |
No changes to template. ACLs are defined in config file, with ' | No changes to template. ACLs are defined in config file, with ' | ||
ACL file: | ACL file: | ||
+ | < | ||
< | < | ||
ref_forunders write {" | ref_forunders write {" | ||
- | *:henvisning write {" | + | :henvisning write {" |
- | ref_forunders: | + | ref_forunders: |
</ | </ | ||
- | Users and roles can be defined as in *Design1*. | + | Users and roles can be defined as in //Design1//. |
+ | |||
+ | =====Client===== | ||
+ | The data received on the client must indicate what features that is to be enabled for the current user, without the client having to make an explicit user lookup. | ||
+ | Example: | ||
+ | <code xml> | ||
+ | <?xml version=' | ||
+ | < | ||
+ | features=" | ||
+ | <macro name=" | ||
+ | <macro name=" | ||
+ | <macro name=" | ||
+ | </ | ||
+ | </ | ||
+ | Making the commit button disabled or invisible and the ' |
pracro/acl.1302516146.txt.gz · Last modified: 2011/04/11 12:02 by deva