Versions Compared

Old Version 6

changes.mady.by.user Fernando Aguilar

Saved on

compared with

New Version 7

changes.mady.by.user Fernando Aguilar

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  • Component A - Service provider
  • Component B - Bring order to chaos
  • Component C - Hide my precious treasure

The components are as follows:

ComponentDescriptionWhy did we choose it?Link
KeycloakKeycloak is an open source Identity and Access Management solution aimed at modern applications and services. It makes it easy to secure applications and services with little to no code.

Keycloak fullfil all the required functionalities expected:

  • Compatible: OIDC (priority), SAML (interesting, eduGain).
  • Federation of 1-N Institutions. Citizen Scientists (Social IDs).
  • Roles Management. Role mapping (e.g. Google users to Citizen Scientist).
  • Identity linking (optional).
  • Group Management. Some groups are allowed to do…
  • Distributed, clustered. High availability. NATIVE
https://www.keycloak.org/
FEUDAL

Federated User Credential Deployment Portal.

One possibility to link between the IdP (Keycloak) and a "non-compatible" service.https://hdf-portal.data.kit.edu/
WaTTS

WaTTS allows using any legacy service with federated identities, such as eduGain or google.

For this, WaTTS accepts federated identities (via OpenID Connect) and uses a plugin scheme to generate credentials for your service. This allows you to provide services that do not normally support federated identities to federated users.

One possibility to link between the IdP (Keycloak) and a "non-compatible" service.https://github.com/indigo-dc/tts


Architecture

This section will provide 2 important parts:

...