...
Panel | |||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| |||||||||||||||
|
Panel | ||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||
|
Activity overview
Panel | ||
---|---|---|
| ||
#Please describe the high-level goal of the incubator Activity, provide an overview of the anticipated work and needed resources and skills. Please also describe how commitment from various partners is warranted. - delete this line after using the template# With the growth of the metadata feeds all over the world, together with the increased need for catering for multiple federations at once, Service Providers are increasingly reliant on the MetaData Query (MDQ) protocol, for Relying Party metadata lookup. In addition, for For MDQ there is only one implementation in common use: pyFF. The MDQ protocol is quite simple however, This is a risk as it creates a high dependence on that piece of technology This activity seeks to simplify the scalable use of MDQ, both for federations that currently operate a MDQ as well as for federations tat do not provide an MDQ service. In addition it wants to create an alternative implementation, next to pyFF, for creating and managing XML metadata. |
Panel | ||
---|---|---|
| ||
The aim is to deliver EntityDescriptors as flat files in such a way this mimics MDQ protocol and combine that with Global DNS to create a super fast and highly redundant distribution mechanism for MDQ. |
...
Panel | ||
---|---|---|
| ||
#Please describe the technical details for the Activity. - delete this line after using the template# Potential features of such an alternative MDX solution are:
|
Panel | ||
---|---|---|
| ||
#What is the business case for the Activity? Who would be beneficiaries of the results of the Activity and what would potential business case look like if applicable? - delete this line after using the template# <Enter here>Better uptimes for metadata availability and thus better uptimes for federated identity management services. |
Panel | ||
---|---|---|
| ||
#Are there risks that influence either the implementation of the activity or its outcomes? - delete this line after using the template# <Enter here> | ||
Complexity caused by the conflicting characteristics of centralizing a decentralized service. |
Panel | ||
---|---|---|
| ||
#How do data protection and privacy impact the Activity? Think about e.g. handling of personal data of users - delete this line after using the template# <Enter here>There is no personal data involved, apart from the technical and security contacts in metadata, which are distributed in the current system in a comparable manner. |
Panel | ||
---|---|---|
| ||
|
...
Activity Results
Panel | ||
---|---|---|
| ||
This activity is still ongoing An architecture for an alternative MDX solution was designed and a working PoC was implemented according to the specifications. |
Meetings
Date | Activity | Owner | Minutes | |
---|---|---|---|---|
15.10.21 | Incubator all-hands | Niels van Dijk | ||
22.02.22 | Public demo | Niels van Dijk | ||
03.05.22 | Final demo | Niels van Dijk | January 1, 2017 | Kickoff meeting |
Documents
Attachments