Child pages
  • Software Requirements for Discovery
Skip to end of metadata
Go to start of metadata

A REFEDS working group focused on the software requirements for Discovery is proposed.  This will be complementary to other work on Discovery but with a tight focus on requirements for SAML software projects.

Overview

As the size of metadata aggregates continues to increase, the pressure to adopt more sensible "just in time" distribution models to endpoints will continue to increase. The community already has draft standards and implementations of at least one such model [1], with at least one major deployment already in use. For at least some Identity Provider implementations, this is largely a solved problem waiting on adoption.

However, some popular Identity Provider Discovery mechanisms currently rely on the use of metadata aggregates to populate lists of Identity Providers with names and logos. Adoption of just-in-time metadata by Service Providers that use such discovery software is contingent on either changing that software, replacing it, or changing the discovery experience itself.

The goal of this working group is to identify feature gaps in currently active software projects, including but not limited to Shibboleth, that need to be addressed in the near term in order to support a transition to just-in-time metadata models, under the assumption that the current aggregates would not be used. The gap analysis would be used to create feature requests for the projects.

It is not a goal of this working group to propose specific discovery solutions, but it will need to identify the most likely solutions to see adoption alongside new metadata distribution models in order to perform a reasonable gap analysis. In a perfect world, there would be a single answer, but this appears unlikely in a time frame useful to the software planning process.

Terms

The following terms apply to all REFEDS Working Groups:


  1. When a working group is agreed, REFEDS Participants will be asked if they wish to participate. Working Groups tend to be small, so consensus can be achieved quickly between participants.
  2. A chair for the group is chosen from the REFEDS Participants.
  3. GÉANT provides facilities for the working group, including meeting support, wiki space, mailing lists and, where appropriate, funding.
  4. An appropriate output from the group is produced. Currently, this is typically a draft white paper or a wiki page.
  5. When the Working Group is in agreement, the chair shares the outputs with the wider REFEDS community with an open period for discussion and comment. This is typically a period of 4 weeks, but may be longer if appropriate.
  6. After this period of time, the REFEDS Steering Committee signs off on the work item. Work is either written up as a formal white paper, left on the wiki but promoted as finished work or occasionally submitted as an Internet Draft.

Chair

TBC

Deliverables

  • a brief summary of current software state for any projects willing to participate.
  • feature requests submitted to any participating software project.

Requirements

  • liaising with any current discovery activities relevant to the community.
  • liaising from any software projects willing to entertain feature request.

Timeline

Work to conclude by the end of 2017.


[1] https://datatracker.ietf.org/doc/draft-young-md-query/

  • No labels