|
Size: 4336
Comment:
|
Size: 3274
Comment:
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 21: | Line 21: |
| The doms auth system is responsible for ensuring that no user can access files without sufficient credentials. Furthermore, no doms record should be viewable without the nessesary credentials. These are two different requirements. | The doms auth system is responsible for ensuring that no user can access files without sufficient credentials. Furthermore, parts or entire doms record should be blockable with the auth system. |
| Line 23: | Line 23: |
| 1. Auth check on bitstorage access 1. Auth check on long post viewing |
The Auth system is based around Fedora as the Authorization provider. Object policies are expressed in Fedora in XACML. There is meant to be a number of Authentication providers. |
| Line 26: | Line 25: |
| == Bitstorage auth design == This design has been worked out between Mads (INITIALS), Per (INITALS) and abr. Jhlj has been informed of some of the design, but need to sign of on the final version. |
The auth system is layered. Authentication happens on the outer layer, against whatever Authentication providers we link with. The trusted services on the outer layer establishes the users roles/attributes. These are then communicated to Fedora, which evaluates them against the authorization policy. |
| Line 29: | Line 27: |
| The design is as follows: | With this design, we can have a single Authorization provider, and thus one place to define policies, but integrate with numerous signon systems. |
| Line 31: | Line 29: |
| Components: * Doms auth checker: Service for checking credentials against the policy in doms. Author IT Digitale Ressourcer * IP2RolesMapper: Service for mapping user ip to a set of roles. Auther Unknown. * URL2FileMapper: Service for mapping a permament url to a file. Authro IT Drift * PHP main app: Service for handling the flow between the services. Auther IT Service * Apache server: Server for housing the php app, and handling the perm urls. Use URL_rewrite to forward requests to php. |
|
| Line 38: | Line 30: |
| 1. Each file in bitstorage is assigned a permanent URL 1. An Apache server is set up to handle these URLs |
=== Components === |
| Line 41: | Line 32: |
| User GETs a perm url 1. Apache -> url_rewrite the requests and forward it to php app 1. Php application 1. Invoke IP2RolesMapper to get user roles. 1. Invoke Doms Auth Checker(url, roles) to see if the IP roles are enough to get the file 1. If no: 1. Extract Wayf credentials from the user, by redirecting him to the WAYF page. 1. Invoke Doms Auth Checker(url, creds) to see if the file is assesible with the creds 1. if no: 1. Send Unauthorized error 1. Invoke URL2FileMapper to get a file location. 1. Open this file. 1. (Request file mime-type from Fedora) 1. Stream it to the user. |
1. Some service that converts user roles into credentials that Fedora can work with 1. A system that transparently handles the credentials when requesting files from bitstorage 1. A system that transparently handles the credentials when displaying Doms objects in Summa |
| Line 56: | Line 36: |
| It can be seen that the php app will become a bottleneck. There are several designs that could work around this. Having several identical apache servers with identical php apps, and using some sort of load balancing would work. === IP Roles are enough === {{attachment:auth2.jpeg}} === Wayf creds needed === {{attachment:auth1.jpeg}} === No creds good enough === {{attachment:auth3.jpeg}} |
Task Doms Auth system
- Title
- Doms Auth system
- State
- Not started
- Time used
- Time estimated
Description
The doms auth system is responsible for ensuring that no user can access files without sufficient credentials. Furthermore, parts or entire doms record should be blockable with the auth system.
The Auth system is based around Fedora as the Authorization provider. Object policies are expressed in Fedora in XACML. There is meant to be a number of Authentication providers.
The auth system is layered. Authentication happens on the outer layer, against whatever Authentication providers we link with. The trusted services on the outer layer establishes the users roles/attributes. These are then communicated to Fedora, which evaluates them against the authorization policy.
With this design, we can have a single Authorization provider, and thus one place to define policies, but integrate with numerous signon systems.
Components
- Some service that converts user roles into credentials that Fedora can work with
- A system that transparently handles the credentials when requesting files from bitstorage
- A system that transparently handles the credentials when displaying Doms objects in Summa
Sub tasks
| Title | State | Time used | Time estimated |
Documentation
Progress history
| Iteration | Time used | Status | Notes | Tasks adressed |