Page MenuHomeSoftware Heritage

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

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 updated the task description. (Show Details)Oct 29 2019, 4:32 PM
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 updated the task description. (Show Details)Jan 23 2020, 4:23 PM
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
anlambert changed the status of subtask T2267: Check OIDC user session state in backend from Open to Work in Progress.Mar 24 2020, 3:28 PM
anlambert updated the task description. (Show Details)Apr 7 2020, 4:13 PM
anlambert closed this task as Resolved.Thu, Jun 18, 2:16 PM

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