-
Notifications
You must be signed in to change notification settings - Fork 218
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ImportError: cannot import name 'JSONWebSignatureSerializer' from 'itsdangerous' #147
Comments
Hello, It was mentioned in #3 ... In your Pipfile, could you please add |
How long can you stay in this deprecated functionality? Instead of going backward, this library should be updated to use proper library as described here: https://itsdangerous.palletsprojects.com/en/2.1.x/changes/ |
I honestly don't know, I had the same issue several days ago and thought it would be helpful to share ;) |
Apparently fixed in #144 |
confirming that installing #144 fixes it. |
Fixed? Install? What do you mean and how? #144 is not even merged yet!? |
@khteh you can install the changes introduced by #144 by specifying directly the MR or the commit you want in your e.g.: On our end, we are using a custom security manager for Airflow to connect using OIDC, which relies on Note that |
What stops you from merging and releasing the fix as a new version? |
@khteh well, one would need to have the proper rights on the repo for that, so this decision relies on @puiterwijk’s approval of the PR. |
Ok. Thanks. BTW, what's |
Sorry, I mixed the Gitlab’s way of defining things. MR = Merge request (which is Gitlab’s denomination for Pull Request). |
For those using |
@puiterwijk could this PR please be merged and released? |
Are there any possible workaround this issue? It seems it will take a while to merge the fix to master. |
Yes. See #147 (comment) |
'flask-oidc' 1.4.0 (latest) still use 'JSONWebSignatureSerializer' which was removed in 'itsdangerous' v2.1. Until puiterwijk/flask-oidc#144 is merged and a new version of flask-oidc is released, it's necessary to pin 'itsdangerous' to a version below 2.1 if 'flask-oidc' is used. References: puiterwijk/flask-oidc#147 https://itsdangerous.palletsprojects.com/en/2.1.x/changes/#version-2-1-0
So it's 2023, 4 months later, is this still the issue and is it not yet updated? |
if it fixed, why dont you get updated? |
Came here hoping for a fix too. |
Regenerate dependencies files with pip-compile-multi (on python 3.8); allow Flask update since connexion was updated to not conflict, but limit it to <2.3 since newer versions pull in a version of werkzeug that's incompatible with connexion (https://github.com/spec-first/connexion/blob/2.14.2/setup.py#L28). Also constrain the version of itsdangerous because of puiterwijk/flask-oidc#147.
Regenerate dependencies files with pip-compile-multi (on python 3.8); allow Flask update since connexion was updated to not conflict, but limit it to <2.3 since newer versions pull in a version of werkzeug that's incompatible with connexion (https://github.com/spec-first/connexion/blob/2.14.2/setup.py#L28). Also constrain the version of itsdangerous because of puiterwijk/flask-oidc#147.
Still waiting on a fix… |
Python 3.10.4
pipenv, version 2022.5.2
flask-oidc 1.4.0
Exception happens on the following import line:
The text was updated successfully, but these errors were encountered: