Apache Superset: Fix JWT problem by updating to flask-jwt-extended 4.7.1

Also, configure `JWT_VERIFY_SUB = False`.
crate · Nov 22, 2024 · 2a17d1e · 2a17d1e
1 parent b1979b1
commit 2a17d1e
Show file tree

Hide file tree

Showing 2 changed files with 7 additions and 1 deletion.
diff --git a/application/apache-superset/requirements.txt b/application/apache-superset/requirements.txt
@@ -1,3 +1,3 @@
 apache-superset
-pyjwt<2.10
+flask-jwt-extended>=4.7.1
 sqlalchemy-cratedb>=0.40.1
diff --git a/application/apache-superset/superset_config.py b/application/apache-superset/superset_config.py
@@ -15,6 +15,12 @@
 # to start and you will see an error in the logs accordingly.
 SECRET_KEY = 'VcKzHS4g2h+dP33tCbqOghtKaU37wvFECMhVqrfccaoI/17qh/j3+VDV'
 
+# Configure JWT subsystem to not enforce that the sub claim is a string.
+# https://github.com/crate/cratedb-examples/issues/741
+# https://github.com/apache/superset/issues/30995
+# https://github.com/dpgaspar/Flask-AppBuilder/issues/2287
+JWT_VERIFY_SUB = False
+
 # The SQLAlchemy connection string to your database backend
 # This connection defines the path to the database that stores your
 # superset metadata (slices, connections, tables, dashboards, ...).