During the last two Testbeds (14 and 15) several remarks have been made regarding usability and standardization of Federation Management use cases. Almost all of them point at the complexity of use of current state-of-the-art technologies (just by taking a look at both OpenIDConnect and User-Managed Access sequence diagrams, it becomes obvious).
There is also an identified need to unify "push" and "pull" architectures for data propagation across Federated environments.
In order to solve this, it would be worthwhile to further analyze the possibility to define a reference Federation Management API similar to the one being developed during Testbed-15:
This should be further modified and improved taking into account more complex use-cases and focusing on community onboarding and related initiatives (such as the Earth Observation Exploitation Platforms Common Architecture use case manual)
During the last two Testbeds (14 and 15) several remarks have been made regarding usability and standardization of Federation Management use cases. Almost all of them point at the complexity of use of current state-of-the-art technologies (just by taking a look at both OpenIDConnect and User-Managed Access sequence diagrams, it becomes obvious).
There is also an identified need to unify "push" and "pull" architectures for data propagation across Federated environments.
In order to solve this, it would be worthwhile to further analyze the possibility to define a reference Federation Management API similar to the one being developed during Testbed-15:
https://testbed15-fm.elecnor-deimos.com/swagger-ui/
This should be further modified and improved taking into account more complex use-cases and focusing on community onboarding and related initiatives (such as the Earth Observation Exploitation Platforms Common Architecture use case manual)
https://eoepca.github.io/