Add support for public clients and PKCE

Created on 15 November 2024, about 1 month ago

Problem/Motivation

Social Auth currently only supports OAuth2 for private clients with a client ID and secret key. Public clients using Proof Key for Code Exchange (PKCE) use only a public client ID and no secret key.

Proposed resolution

Add support for getting and setting a PKCE code that can be used by the underlying OAuth2 client for code challenge and verification.

Remaining tasks

Create and merge a PR.

API changes

Add a new uses_public_client_id option to the network plugin configuration. Implementers can use this option to indicate their client uses a public Client ID and does not require a secret key,

πŸ“Œ Task
Status

Active

Version

4.2

Component

Code

Created by

πŸ‡ΊπŸ‡ΈUnited States wells Seattle, WA

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

Merge Requests

Comments & Activities

Production build 0.71.5 2024