Output – FAR – Adding Shibboleth to DSpace With CASAK

Output Name: Output – FAR – Adding Shibboleth to DSpace With CASAK

Title: Adding Shibboleth to DSpace With CASAK
Number of pages or page numbers: webpage

Date Released: unknown

URI for Output: https://dspace.far-project.lse.ac.uk/casak-shib.html (report) for

patch – https://saffron.caret.cam.ac.uk/svn/projects/far/trunk/

Summary of contents:

CASAK is a patch for DSpace which allows container auth to be integrated into DSpace. It provides a number of mapping and filtering facilities to transform data provided by the container into a form suitable for DSpace. These facilities are generally inferior to those available within the SP, but for simple cases the configuration is perhaps simpler.

Configuring CASAK to use Shibboleth is therefore simpler than many use-cases of CASAK.

The approach used here contrasts with that used in MAMS in that CASAK is not Shibboleth specific, and has been designed to make a range of container auth solutions possible with CASAK. The purpose of this was to increase the long-term sustainability of the patch by extending its application to as broad a user-base as possible.

Output – FAR – LDAP server containing sample users with these attributes

Output Name: Output – FAR – LDAP server containing sample users with these attributes

Title: LDAP server containing sample users with these attributes
Number of pages or page numbers: webpage

Date Released: 29 June 2008

URI for Output: https://gabriel.lse.ac.uk/twiki/bin/view/Projects/FAR/FARProjectDemonstratorArchitecture

Summary of contents:

Technical description of the FAR Demonstrator Architecture.

Output – FAR – FAR attribute requirements report

Output Name: Output – FAR – FAR attribute requirements report

Title: FAR attribute requirements report
Number of pages or page numbers: webpage

Date Released: 19 August 2008

URI for Output:  https://gabriel.lse.ac.uk/twiki/bin/view/Projects/FAR/AttributeUseReport

Summary of contents:

  • Requirements for specific attributes to be used for Federated Access Management (FAM)-mediated access to repositories are not necessary because repository products use groups for access control already
  • It is recommended that group membership information is structured in attribute stores on a per-user basis (with a user object containing a list of groups of which the user is a member) as opposed to solely as a per-group basis (with a group object containing a list of members)
  • The use of groups for authorisation means that it should be possible for FAM to continue to be applicable with the introduction of new features to repository software

Project – FAR

Federated Access to Repositories

Project Name: Federated Access to Repositories

Programme Name: Digital Repositories programme

Strand: Interoperability Demonstrators

JISC Project URI: http://www.jisc.ac.uk/whatwedo/programmes/programme_rep_pres/interoperabilitydemos/far.aspx

Project URI:https://gabriel.lse.ac.uk/twiki/bin/view/Projects/FAR/WebHome

Start Date:01/11/2007

End Date:31/07/2008

Governance: Integrated Information Environment Committee (JIIE)

Contact Name and Role: John Paschoud, Project Manager

Brief project description: A workshop at the OAI5 conference in April 2007 identified a need for improved attribute managed federated access to repositories, and produced a set of requirements. The Federated Access to Repositories (FAR);project would take up this list, and use it to: Create recommendations for attributes to describe authorisation to repositories; where appropriate,;these recommendations will be passed to relevant standards groups Develop extensions to the repository software (EPrints and DSpace) so that it can be used with; Shibboleth and meet these requirements (building on earlier work where this exists) ;Test existing work integrating Shibboleth and Fedora and recommend to developers what will be;needed to meet these requirements ;Install demonstration repositories to show how this can work in practice Feed the modifications and full documentation into the appropriate repository software development process to ensure maintenance through future releases of Eprints and Shibboleth Develop procedures to consider ways of extending federated access management to new functionality introduced into the repository software products following the conclusion of the project A demonstrator of the software will be produced as well as a final version.

Name of Trawler: Mahendra Mahey