Suggest changing your secret key to force all users to get the new format of Using will not work correctly if they utilize additional claims. This has the unfortunate side effect that any existing JWTs your application is Which was not previously possible in this extension. Important benefit of allowing you to override reserved claims (such as ``nbf``)
Instead of inside the the nested ``user_claims`` dictionary. JWTs with additional claims, those claims are put on the top level of the token, The ``JWT_USER_CLAIMS`` configuration option has been removed. Here is everything you will need to be aware of when Of all these changes, this extension should be simpler to use, provide moreįlexibility, and allow for easier additions to the API without introducingįurther breaking changes.
BreakingĬhanges are never fun, but I really believe they are for the best. This release includes a lot of breaking changes that have been a long time coming,Īnd will require some manual intervention to upgrade your application.
0 kommentar(er)
