[Epic] Authenticate users in the Challenge Registry

[tschaffter]

The objective is to make the Challenge Registry a user-centered apps to offer features that users can customize. The motivation is also to involve users in the data curation effort, e.g. by allowing them to indicate whether they participated in challenge X. The scope of this ticket is to enable the users to authenticate using a local account as well as SSO (e.g. Google accounts, Synapse accounts, etc.).

• Evaluate third-party solutions for authorization #125
• Evaluate Keycloak #126
• Enable users to fetch their profile data using authentication through keycloak #184
• Export and import Keycloak realm and users programmatically #186
• Evaluate overture.bio #187
• Prototype access to API resources using Keycloak #188
• Override KC realms and users when importing from files #193
• Setup Sign in with Google using Keycloak #211
• Integrate keycloak to microservice infra #246
• Generate challenge-keycloak h2 files using docker run instead of docker-compose #266
• Remove Sage identity provider data from this repo #268
• Create endpoint to sign in #319
• Add user data to SQL table #463

Future work

• Integrate AuthService with KeycloakService #224

[tschaffter]

Added to Sprint 22.09. By the end of this sprint, the user should be able to login, logout and retrieve their profile information. The extended objective is to enable the user to update their profile information. User registration and password recovery are planned for 22.10.

[tschaffter]

Sprint 22.09 Review

This Epic is almost complete. The remaining PR (#224) has most of the code required to login and log out. This Epic can be closed once the following tasks are completed:

• feat(api-client): regenerate the API client for Angular #747
• Integrate AuthService with KeycloakService #224

These tasks should be completed by the end of the first week of Sprint 22.10.

Update

• The user can now login and logout in the app (feat(app): Authenticate the user using Keycloak #444).
• Integrate AuthService with KeycloakService #224 will be implemented during the Spring 22.10.