Ticket #975 (closed task: wontfix)

Opened 11 years ago

Last modified 10 years ago

Scope out the implications of securing modular WCS/WMS

Reported by: spascoe Owned by: spascoe
Priority: required Milestone: Reporting
Component: COWS Version:
Keywords: Cc:

Description (last modified by spascoe) (diff)

This is an action from the  2008-05-09 DCIP meeting.

In order to move all our code to the new ows_common we need to work out how easy it will be to separate the WCS from the discovery portal (ows_server) whilst keeping NDG-security.

See #1004 for Phil's security WSGI middleware.

Change History

comment:1 Changed 11 years ago by lawrence

  • Component changed from WCS to COWS

comment:2 Changed 11 years ago by spascoe

  • Description modified (diff)

comment:3 Changed 11 years ago by pjkersha

#1005 and #1006 are also relevant.

  • Security as implemented with ows_server used the NDG Browse Policy Decision Point i.e. security constraints from a resource were extracted directly from the MOLES or CSML document.
  • For NDG3 a completely new PDP will have a component (#1006) to link resource URI(s) to security constraints independent of the resource (file, doc etc.) itself.

comment:4 Changed 10 years ago by domlowe

  • Status changed from new to closed
  • Resolution set to wontfix

The WCS has already been moved out of ows_server and into cows. Security is now a separate issue.

Note: See TracTickets for help on using tickets.