fix(deps): update dependency django-oauth-toolkit to v3 #3252
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
1.7.1
->3.0.1
Release Notes
jazzband/django-oauth-toolkit (django-oauth-toolkit)
v3.0.1
Compare Source
Fixed
v3.0.0
Compare Source
WARNING - POTENTIAL BREAKING CHANGES
AbstractAccessToken
model require doing amanage.py migrate
after upgrading.manage.py makemigrations
).Added
LoginRequiredMiddleware
introduced in Django 5.1.Changed
pk
instead ofid
. This enables, for example, custom swapped models to have a different primary key field.This adds a SHA-256
token_checksum
field that is used to validate tokens.database to use instead of assuming that 'default' is the correct one.
Removed
RedirectURIValidator
,WildcardSet
per #1345;validate_logout_request
per #1274Fixed
ui_locales
request parameter triggersAttributeError
under certain circumstancesSecurity
REFRESH_TOKEN_REUSE_PROTECTION
.In combination with
ROTATE_REFRESH_TOKEN
,this prevents refresh tokens from being used more than once. See more at
OAuth 2.0 Security Best Current Practice
v2.4.0
Compare Source
WARNING
Issues caused by Release 2.0.0 breaking changes continue to be logged. Please make sure to carefully read these release notes before
performing a MAJOR upgrade to 2.x.
These issues both result in
{"error": "invalid_client"}
:The application client secret is now hashed upon save. You must copy it before it is saved. Using the hashed value will fail.
PKCE_REQUIRED
is nowTrue
by default. You should use PKCE with your client or setPKCE_REQUIRED=False
if you are unable to fix the client.If you are going to revert migration 0006 make note that previously hashed client_secret cannot be reverted!
Added
OAuth2ExtraTokenMiddleware
for adding access token to request.See Setup a provider in the Tutorial.
post_logout_redirect_uris
field in the Application Registration formHS256 keys.
This means your client secret will be stored in cleartext but is the only way to successfully use HS256 signed JWT's.
code_challenge_methods_supported
property to auto discovery information, per RFC 8414 section 2Fixed
EXP
in AccessToken always as UTC instead of (possibly) local timezone.Use setting
AUTHENTICATION_SERVER_EXP_TIME_ZONE
to enable different time zone in case the remoteauthentication server does not provide EXP in UTC.
on how to create a code challenge and code verifier
0006_alter_application_client_secret
. Note that reversing this migration cannot undo a hashedclient_secret
.RedirectURIValidator
in favor ofAllowedURIValidator
.validate_user
.Removed
v2.3.0
Compare Source
WARNING
Issues caused by Release 2.0.0 breaking changes continue to be logged. Please make sure to carefully read these release notes before
performing a MAJOR upgrade to 2.x.
These issues both result in
{"error": "invalid_client"}
:The application client secret is now hashed upon save. You must copy it before it is saved. Using the hashed value will fail.
PKCE_REQUIRED
is nowTrue
by default. You should use PKCE with your client or setPKCE_REQUIRED=False
if you are unable to fix the client.Added
Changed
cleartokens
management commandv2.2.0
Compare Source
Added
Changed
Fixed
v2.1.0
Compare Source
Added
prompt=login
for the OIDC Authorization Code Flow end user Authentication Request.Changed
createapplication
management command enhanced to display an auto-generated secret before it gets hashed.Fixed
v2.0.0
Compare Source
This is a major release with BREAKING changes. Please make sure to review these changes before upgrading:
Added
This completes the view to provide all the REQUIRED and RECOMMENDED OpenID Provider Metadata.
on using Celery to automate clearing expired tokens.
Changed
PKCE enabled will fail to authenticate. This breaks with section 5 of RFC7636
in favor of the OAuth2 Security Best Practices for Authorization Code Grants.
If you want to retain the pre-2.x behavior, set
PKCE_REQUIRED = False
in your settings.pyclient_secret values. This is a breaking change that will migrate all your existing
cleartext
application.client_secret
values to be hashed with Django's default password hashing algorithmand can not be reversed. When adding or modifying an Application in the Admin console, you must copy the
auto-generated or manually-entered
client_secret
before hitting Save.If you've customized OIDC responses
and want to retain the pre-2.x behavior, set
oidc_claim_scope = None
in your subclass ofOAuth2Validator
.access_token
available toget_oidc_claims
when called fromget_userinfo_claims
.--algorithm
argument tocreateapplication
management commandFixed
validate_bearer_token()
to properly setrequest.scopes
to the list of granted scopes.--skip-authorization
argument of thecreateapplication
management command.Removed
urn:ietf:wg:oauth:2.0:oob
andurn:ietf:wg:oauth:2.0:oob:auto
which are replacedby RFC 8252 "OAuth 2.0 for Native Apps" BCP. Google has
deprecated use of oob with
a final end date of 2022-10-03. If you still rely on oob support in django-oauth-toolkit, do not upgrade to this release.
Configuration
📅 Schedule: Branch creation - "every weekend" in timezone US/Eastern, Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.