Page MenuHomeSoftware Heritage

Use OpenID Connect to authenticate and authorize users in Django
Closed, MigratedEdits Locked

Description

As the decision has been made to use Keycloak as identity provider for Software Heritage, we need to add
support for OpenID Connect into the Django authentication layer.

To do so, we could inspire from or directly use one of these existing Django applications:

Event Timeline

anlambert renamed this task from Integrate Keycloak in Django authentication layer to Use OpenID Connect to authenticate users in Django.Jan 23 2020, 3:39 PM
anlambert updated the task description. (Show Details)
anlambert renamed this task from Use OpenID Connect to authenticate users in Django to Use OpenID Connect to authenticate and manage users in Django.Jan 23 2020, 4:26 PM
anlambert renamed this task from Use OpenID Connect to authenticate and manage users in Django to Use OpenID Connect to authenticate and authorize users in Django.Jan 23 2020, 4:29 PM

All required authentication features are now implemented in swh-web, closing this.

gitlab-migration changed the status of subtask T2246: Add custom Django model for remote users from Resolved to Migrated.
gitlab-migration changed the status of subtask T2247: Map Keycloak permissions to Django ones from Resolved to Migrated.
gitlab-migration changed the status of subtask T2248: Check OIDC user session state in frontend from Wontfix to Migrated.
gitlab-migration changed the status of subtask T2249: Add Web API authentication based on bearer tokens from Resolved to Migrated.
gitlab-migration changed the status of subtask T2267: Check OIDC user session state in backend from Resolved to Migrated.
gitlab-migration changed the status of subtask T2295: Map Keycloak staff user group to django one from Resolved to Migrated.