Skip to content

Feature/kanidm allow ability to enable PKCE#1421

Merged
atymic merged 2 commits intoSocialiteProviders:masterfrom
eric-hansen:feature/kanidm-pkce-default
Feb 3, 2026
Merged

Feature/kanidm allow ability to enable PKCE#1421
atymic merged 2 commits intoSocialiteProviders:masterfrom
eric-hansen:feature/kanidm-pkce-default

Conversation

@eric-hansen
Copy link
Copy Markdown
Contributor

Kanidm heavily encourages PKCE for OAuth2 clients. While one can disable PKCE for legacy support, this poses a security concern, and there is no guarantee this feature will continue.

Really, I am not sure if this is the best way to approach this, but it seemed clean enough. I didn't see a reason why this couldn't be set up as a config option. Kanidm treats OAuth2 setups as clients themselves (e.g., an app that uses Kanidm either needs to create a new OAuth2 client in Kanidm or use grouping trickery).

(re-opening #1420 as a non-org account.)

@atymic atymic merged commit c4db726 into SocialiteProviders:master Feb 3, 2026
5 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants