gbmichael28 commented on issue #24579:
URL: https://github.com/apache/superset/issues/24579#issuecomment-1666878013
I have the same issue. I have TALISMAN_ENABLE as False in config.py.
# Do you want Talisman enabled?
#TALISMAN_ENABLED = utils.cast_to_boolean(os.environ.get("TALISMAN_ENABLED",
True))
TALISMAN_ENABLED = utils.cast_to_boolean(os.environ.get("TALISMAN_ENABLED",
False))
(I comment out the original line, and then copy and paste into a new line
and change True to False).
Type in the username and password as specified, and voila, it goes right
back to the same login page.
I am running the docker-compose-non-dev.yml (but I get the same result with
the regular docker-compose). I do a have a SECRET_KEY defined in the
superset_config.py file. I have defined it two ways. The first time, I
defined it AFTER I'd already brought Superset up. The second time, I defined
it before I brought it up. It does not matter either way, it still goes right
back to the login page.
I know the init script is running based on the information below, so the
admin user is created and available.
######################################################################
superset_init |
superset_init |
superset_init | Init Step 1/4 [Complete] -- Applying DB migrations
superset_init |
superset_init |
superset_init |
######################################################################
superset_init |
superset_init |
superset_init |
######################################################################
superset_init |
superset_init |
superset_init | Init Step 2/4 [Starting] -- Setting up admin user
( admin / admin )
superset_init |
superset_init |
superset_init |
######################################################################
superset_init |
superset_worker | [2023-08-06 14:07:04,434: INFO/MainProcess]
Connected to redis://redis:6379/0
superset_worker | [2023-08-06 14:07:04,435: INFO/MainProcess]
mingle: searching for neighbors
superset_init | logging was configured successfully
superset_init | 2023-08-06
14:07:05,241:INFO:superset.utils.logging_configurator:logging was configured
successfully
superset_init | 2023-08-06 14:07:05,243:INFO:root:Configured event
logger of type <class 'superset.utils.log.DBEventLogger'>
superset_worker | [2023-08-06 14:07:05,439: INFO/MainProcess]
mingle: all alone
superset_worker | [2023-08-06 14:07:05,445: INFO/MainProcess]
celery@66f27eab0157 ready.
superset_init | Loaded your LOCAL configuration at
[/app/docker/pythonpath_dev/superset_config.py]
superset_init | Recognized Database Authentications.
superset_init | Admin User admin created.
superset_init |
superset_init |
######################################################################
superset_init |
superset_init |
superset_init | Init Step 2/4 [Complete] -- Setting up admin user
superset_init |
superset_init |
superset_init |
######################################################################
superset_init |
superset_init |
superset_init |
######################################################################
superset_init |
superset_init |
superset_init | Init Step 3/4 [Starting] -- Setting up roles and
perms
superset_init |
superset_init |
superset_init |
######################################################################
Step 4 was also successful, I just excluded it here to save on my novella.
When I changed the secret key AFTER deployment, I did follow the
instructions in the Superset documentation to Rotate in a new SECRET_KEY.
(including viewing the existing from the superset shell inside of the superset
container.
Am I setting the TALISMAN_ENABLED incorrect?
--
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]
