Keycloak satisfy all the expected functionalities, since is is compatible with the most used technologies (SAML, OIDC), it allow IdP federation and allows user group management and attribute mapping. The characteristics provided make Keycloak a promising solution to be adopted instead other available.

Components

This section will contain a lists of components used for this pilot.

It is not required to add a detailed description for each component, but 3 important parts are:

Add Link to component web page
Add a short description to explain its function (not more than 1 raw)
Explain why these components have been chosen

An example:

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

The components are as follows:

...

Use cases can be represented in the form of a table, where:

The title is the use case
Each line is a step
2 columns available, first with text and description, second with a screenshot

(Here's a valid example LINK)

Use Case 1 - Access to service

Access to Rshiny (for the moment)
1.	Access RShiny research service to analyze/calculate thermoclines in water columns.	Image Added
2.	The User is redirected to LifeWatch IdP	Image Added
3.	You can select among the list of federated institutions belonging LifeWatch. For example, IFCA SSO will redirect you to the IFCA IdP	Image Added
4.	Overview of attributes being shared (to authenticate and perhaps authorize)......	Image Added
5b.	The user is successfuly redirected to Rshiny app	Image Added