jcjveraa commented on issue #37842: URL: https://github.com/apache/superset/issues/37842#issuecomment-3890624171
Hi there, chipping in as I'm hitting the exact same with a fresh install, I suggest this is a rather critical bug. Reproducer: Set up a fresh install using the Helm chart, with a custom override in the helm chart for setting the key. I have verified that this key is indeed the one loaded using the 'get current config' commands [from here](https://superset.apache.org/docs/configuration/configuring-superset/#rotating-to-a-newer-secret_key). ```yaml configOverrides: secretKey: | # ref https://superset.apache.org/docs/security/securing_superset/#superset_secret_key-management-critical SECRET_KEY = 'thisIsABadKey' ``` Try to rotate the key by setting these ```yaml configOverrides: secretKey: | # ref https://superset.apache.org/docs/security/securing_superset/#superset_secret_key-management-critical PREVIOUS_SECRET_KEY = 'thisIsABadKey' SECRET_KEY = '2cM+byann7KQHENZ2CTOWX2RcHYqMBlR7HPKitTXyU90Libl+QeKmDNb' # randomly generated for this example of course ``` verify again that these variables are loaded in the flask app, and run `superset re-encrypt-secrets`. Result the same as the poster of this issue: it finishes rather quickly with no errors, but when I try to load data it fails. After rolling back to the old `thisIsABadKey` I can load data again. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
