Replace Bakery with KeyCloak SSO & social sign on

Created on 3 February 2023, over 1 year ago
Updated 18 April 2024, 2 months ago

Problem/Motivation

Drupal.org needs to update past Drupal 7. There will be a transition time when we have both D7 & D9+ sites. These need single sign on (SSO) with each other. Our SSO solution for D7 & earlier is a Drupal module called Bakery. Instead of updating & continuing to maintain Bakery, the Drupal Association has chosen to use a 3rd-party service for login & SSO, KeyCloak.

In addition to SSO, KeyCloak will be used to enable social sign on. This will make starting to contribute to Drupal a little easier, replacing the need to make a new login just for Drupal.org.

The codebases for our Keycloak extensions and migration are at https://gitlab.com/drupal-infrastructure/sso

Proposed resolution

Our KeyCloak instance will be hosted by a 3rd party. In general, we’ll do an incremental migration, test thoroughly, and eventually switch to it as the way to log into Drupal.org.

Remaining tasks

Will be organized in child issues.

User interface changes

KeyCloak will render & host login and related pages. Some tasks, like changing your password, will be done on KeyCloak instead of Drupal.

Data model changes

User accounts will remain as-is.

🌱 Plan
Status

Needs review

Component

Other

Created by

πŸ‡ΊπŸ‡ΈUnited States drumm NY, US

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Comments & Activities

Production build 0.69.0 2024