Ticket #963 (closed task: fixed)

Opened 13 years ago

Last modified 13 years ago

[S] Standalone Gatekeeper with Resource API

Reported by: pjkersha Owned by: pjkersha
Priority: required Milestone: PROD Final
Component: security Version:
Keywords: OMII-UK, security Cc:

Description (last modified by pjkersha) (diff)

The Gatekeeper is currently integrated into the Pylons NDG Browse framework. It needs to be refactored into a separate package.

It also needs a resource API. This provides an interface to map resource ID -> resource attributes (roles) controlling access to it. Data providers will potentially each have a different mechanism to relate the two. One example would be a database interface with tables to store the mapping information. Data providers can apply their own plugin tailored to their needs.

Change History

comment:1 Changed 13 years ago by pjkersha

  • Status changed from new to assigned

comment:2 Changed 13 years ago by pjkersha

  • refactored as standalone PEP (Policy Enforcement Point) and PDP (Policy Decision Point) module/packages under ndg.security.common.authz
  • moles.py PDP version for use with Browse - todo: re-integrate into Browse stack
  • ftpaccess.py: PDP to BADC Data Browser - also developed Perl CGI code to call this and integrate into the BADC Data Browser.

comment:3 Changed 13 years ago by pjkersha

  • Status changed from assigned to closed
  • Resolution set to fixed
  • Description modified (diff)

Completed Browse PDP and re-integrated and tested with ows_server Browse code stack.

Note: See TracTickets for help on using tickets.