Change Details

In order to simplify the use of Keycloak in Django, it should be plugged into the Django authentication layer. To do so, we could inspire from or directly use one of these existing Django applications: - [[ https://github.com/Peter-Slump/django-keycloak | `django-keycloak` ]] - [[ https://github.com/jhuapl-boss/django-oidc.git | `django-oidc` ]], [[ https://github.com/jhuapl-boss/drf-oidc-auth.git | `drf-oidc-auth` ]], [[ https://github.com/jhuapl-boss/boss-oidc.git | `boss-oidc` ]] - [[ https://github.com/mozilla/mozilla-django-oidc | `mozilla-django-oidc` ]]

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: - [[ https://github.com/Peter-Slump/django-keycloak | `django-keycloak` ]] - [[ https://github.com/jhuapl-boss/django-oidc.git | `django-oidc` ]], [[ https://github.com/jhuapl-boss/drf-oidc-auth.git | `drf-oidc-auth` ]], [[ https://github.com/jhuapl-boss/boss-oidc.git | `boss-oidc` ]] - [[ https://github.com/mozilla/mozilla-django-oidc | `mozilla-django-oidc` ]]

In order to simplify the use ofAs the decision has been made to use Keycloak in Djangoas identity provider for Software Heritage, it should be pluggedwe 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: - [[ https://github.com/Peter-Slump/django-keycloak | `django-keycloak` ]] - [[ https://github.com/jhuapl-boss/django-oidc.git | `django-oidc` ]], [[ https://github.com/jhuapl-boss/drf-oidc-auth.git | `drf-oidc-auth` ]], [[ https://github.com/jhuapl-boss/boss-oidc.git | `boss-oidc` ]] - [[ https://github.com/mozilla/mozilla-django-oidc | `mozilla-django-oidc` ]]