Dear Superset Support Team, We are running Apache Superset locally using Docker (docker-compose.yml and docker-compose-non-dev.yml) and are facing issues applying a password policy. Question: How can we properly configure and activate a password policy in Superset? Example of the intended policy: Minimum 8 characters At least 1 letter At least 1 digit At least 1 special character What we have tried so far: 1. Defined a custom password policy using CUSTOM_SECURITY_MANAGER and PASSWORD_VALIDATORS in superset_config.py. 2. Ensured the config file is loaded inside the container. 3. Rebuilt and restarted the containers, cleared the cache. 4. Tested password creation and reset via the UI — the policy is not enforced, for example, password 123 is accepted.
As a temporary workaround, we consider creating a user guide that documents the password rules, but ideally, we would like to have proper enforcement through the system. We would appreciate any guidance or a working example on how to enable password validation in Superset. -- Отправлено из Mail для Android
