Ticket #569 (closed issue: wontfix)

Opened 15 years ago

Last modified 15 years ago

[WG] Define interface to eXist that respects NDG security

Reported by: domlowe Owned by: lawrence
Priority: blocker Milestone: BETA
Component: community Version:
Keywords: Cc:


We've spoken before of a interface to eXist that respects NDG security and can be used to retrieve a secure document (this is a requirement for csml docs).

It has cropped up in various other tickets: 511 437

and in the python coding review PythonCoding ..

I think the first thing to do is to work out how we are going to do this and I think this requires some discussion. Do we want to buld on the discovery webservice? do we want a separate lightweight service? - we know we can access exist from python, is this preferable?

I've made this a WG ticket for now as I think this is a fairly key component that's not well defined.

Change History

comment:1 Changed 15 years ago by selatham

  • Owner changed from selatham to lawrence

Yes - we'll need this for Browse as well (if we have secure MOLES content). Has Bryan had any thoughts on this yet? I know Browse implements security when passing off to DataExtractor. Can we separate this out from Browse and re-use for any situation where security is required?

comment:2 Changed 15 years ago by ko23

I suspect that  eXist and XACML support documentation is useful.

comment:3 Changed 15 years ago by lawrence

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

we have this now once we implement browse security properly in the new wsgi architecture ...

Note: See TracTickets for help on using tickets.