connect EOTDL to IdP(s) also used with authentication for openEO

[achtsnits]

currently EOTDL is federating via openID connect to Auth0 as only IdP

needs to be aligned what options should be supported in future

• openEO on CDSE (with their own keycloak based https://identity.dataspace.copernicus.eu/)
• openEO platform (which uses EGI Federation services via https://www.egi.eu/service/check-in/)

[tatimars]

Sorry, I procede to eliminate the duplicated on this issue and leave here the comment from @achtsnits :
On technical level this is understood - one main question is if you want to keep Auth0 and configure further federation from there or just stick to one provider like EGI (which will then federate to e.g. GitHub)

[Patrick1G]

the goal is that users only have to authenticate/login once, and be able to use EOTDL and any processing that would occur via openEO (either on openEO platform or on openEO CDSE).

CDSE currently has their own identification/authentication system (creating a DB of users/credentials).
Federated ID providers such as EGI checkin do not collect user data and thus no issues with GDPR.

openEO platform uses EGI check in (via openID connect).
I was told that CDSE is planning to use EGI check-in but this is not yet operational and unclear when it will be rolled out.

[juansensio]

I propose to discuss this issue in detail on our upcoming MS5 workshop, and draft the architecture of the system to identify elements involved and the required changes to the current solution.