You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
feat: Update PKCE_REQUIRED to true by default (#1129)
* feat: default PKCE_REQUIRED to True
BREAKING CHANGE: set to False to maintain legacy behavior
Co-authored-by: Alan Crosswell <[email protected]>
Co-authored-by: pre-commit-ci[bot] <66853113+pre-commit-ci[bot]@users.noreply.github.com>
Copy file name to clipboardExpand all lines: CHANGELOG.md
+5Lines changed: 5 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -25,6 +25,11 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
25
25
on using Celery to automate clearing expired tokens.
26
26
27
27
### Changed
28
+
*#1129 (**Breaking**) Changed default value of PKCE_REQUIRED to True. This is a **breaking change**. Clients without
29
+
PKCE enabled will fail to authenticate. This breaks with [section 5 of RFC7636](https://datatracker.ietf.org/doc/html/rfc7636)
30
+
in favor of the [OAuth2 Security Best Practices for Authorization Code Grants](https://datatracker.ietf.org/doc/html/draft-ietf-oauth-security-topics#section-2.1).
31
+
If you want to retain the pre-2.x behavior, set `PKCE_REQUIRED = False ` in your settings.py
32
+
28
33
*#1093 (**Breaking**) Changed to implement [hashed](https://docs.djangoproject.com/en/stable/topics/auth/passwords/)
29
34
client_secret values. This is a **breaking change** that will migrate all your existing
30
35
cleartext `application.client_secret` values to be hashed with Django's default password hashing algorithm
0 commit comments