Difference between revisions of "ESciDoc Authorization Authentication"
Jump to navigation
Jump to search
| Line 2: | Line 2: | ||
== | === What is authorized == | ||
====Core services==== | |||
# | Core services authorize each method of a core service based on a role definition. A role definition can be: | ||
# unlimited (i.e. administrator - can invoke any service method operation) | |||
# limited (i.e. based on properties of the resource ) | |||
More details on the core service authorization concept in [https://zim01.gwdg.de/repos/smc/tags svn, framework_release, cpt_authorization_authentication] | |||
=== | |||
#How solutions authorize? | #How solutions authorize? | ||
#What solutions authorize? | #What solutions authorize? | ||
[[Category:eSciDoc]] | [[Category:eSciDoc]] | ||
Revision as of 11:00, 11 October 2007
Please use this page to discuss in general on the authorization mechanisms for core services, solutions etc.
= What is authorized
Core services
Core services authorize each method of a core service based on a role definition. A role definition can be:
- unlimited (i.e. administrator - can invoke any service method operation)
- limited (i.e. based on properties of the resource )
More details on the core service authorization concept in svn, framework_release, cpt_authorization_authentication
=
- How solutions authorize?
- What solutions authorize?