|
⇤ ← Revision 1 as of 2008-06-26 12:26:09
Size: 365
Comment: Created by the PackagePages action.
|
Size: 582
Comment:
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 1: | Line 1: |
| = LDAP API = | = Authentication API = |
| Line 3: | Line 3: |
| To authenticate to the DOMS system, users must be validated against the Statsbiblioteket LDAP. | DOMS will use the Fedora authentication system to authenticate users of the system. |
| Line 5: | Line 5: |
| The authenticated user must then be passed to the http server to authenticate connection to Fedora. | This means that authentication is handled by using the HTTP authentication mechanism used by Fedora. |
| Line 7: | Line 7: |
| See http://www.fedora-commons.org/documentation/3.0b2/userdocs/server/security/securingrepo.html - we will use the LdapFilterForAttributes filter. | Best practice is using the function ["Fedora 3.0 API/Access#describMethod"] to check credentials on first login. In TestBed we will simply be using fedora-users.xml to define users. In the final production system, see http://www.fedora-commons.org/documentation/3.0b2/userdocs/server/security/securingrepo.html - we will use the LdapFilterForAttributes filter. |
Authentication API
DOMS will use the Fedora authentication system to authenticate users of the system.
This means that authentication is handled by using the HTTP authentication mechanism used by Fedora.
Best practice is using the function ["Fedora 3.0 API/Access#describMethod"] to check credentials on first login.
In TestBed we will simply be using fedora-users.xml to define users. In the final production system, see http://www.fedora-commons.org/documentation/3.0b2/userdocs/server/security/securingrepo.html - we will use the LdapFilterForAttributes filter.