...
- Authentication answers the question "who is the person, and how do I verify that they are who they say they are?" Fedora 4 relies on the web servlet container to answer this question.
- Authorization answers the question, "does this person have permission to do what they want to do?". Fedora 4 provides three different ways to answer this question:
- Simple servlet container authentication. Anyone who has authenticated through the web application container (Tomcat, Jetty, WebSphere, etc.) has permission to do everything – in effect all, authenticated users are superusers.
- WebAC authorizations. Authenticated users' access to resources is mediated by WebAC Access Control Lists stored in the repository.
- [Deprecated] Basic Access Roles authorizations (RBACL). Authenticated users are mapped onto one or more preconfigured roles; a user's role determines what they have permission to do.
- [Deprecated] XACML authorizations. Policies created using the XACML framework are used to determine what operations are permissible to whom, using user and resource properties exposed to the XACML engine.
Servlet Container Configuration
...
| Include Page | ||||
|---|---|---|---|---|
|
...
Bypassing Authorization
| Include Page | Access Roles Module | Access Roles Module |
|---|
...
|
WebAC Authorization Delegate
includeWebAC Authorization Delegate
Basic Role-based Authorization Delegate
| Warning |
|---|
As of Fedora 4.7.4, the RBACL authorization modules is officially deprecated, and will not be included in future releases of Fedora. Subsequent Fedora releases will only include the WebAC authorization module. |
Basic Role-based Authorization Delegate (RBACL)
XACML Authorization Delegate
...
| Warning |
|---|
As of Fedora 4.7.4, the XACML authorization modules is officially deprecated, and will not be included in future releases of Fedora. Subsequent Fedora releases will only include the WebAC authorization module. |
Bypassing Authorization
Include Page