Difference between revisions of "Federation Trust Registry"

Revision as of 17:45, 14 September 2018

Full Title or Meme

Wherever a Web Sites wishes to take advantage of the benefits of belonging to a Federation it needs to be exposed in a Data Service that allows any user to ensure that the Web Site has been Validated by the Federation.

Context

Several variations on the theme of a Federation Trust Registry exist already.

• Trust Services of TSCP the Transglobal Secure Collaboration Program (mostly focused on NATO A&D industry).
• UK Open Banking (focused on UK banks and payment processors)
• Recognized Coordinating Entity (RCE) (focused on the US Health Care community.)

Problem

So far every solution has been one-off and not applicable to the next federation with the same general problem.

Solution

In order that a Federation can be expose both is principles and its membership to the public some data server needs to provide information about the existing membership and their status. There are two ways to do this:

1. A list of the members and their status that can be viewed in a browser.
2. A data service that exposes the contents of the site in machine readable format.

This page is about the later case.

Of primary importance for a Federation that wants to allow user's to trust the members, is some easily accessible data service on a site that meets the following criteria^[1]

1. Reliable, always-on accessibility.
2. Meta-data descriptions of the contents of the site.
3. Machine readable data as well as meta-data (called Service-Enabled Data Store).
4. Data Security

References

1. ↑ Michael J. Carey +2, Data Services (2012-06) CACM 55 No 6 Pp. 86-97

External Sources

• OAuth 2.0 Dynamic Client Registration Protocol RFC 7591
• Email thread that suggests use of software statements to provide federation.
• Application Bridging for Federated Access Beyond Web (ABFAB) Use Cases RFC 7832.