Replies: 2 comments 1 reply
-
Hail, @otailai 👋 Welcome to Fief's kingdom! Our team will get back to you very soon to help. In the meantime, take a minute to star our repository ⭐️ Farewell! |
Beta Was this translation helpful? Give feedback.
0 replies
-
Good catch! We could indeed proactively verify the password in the CLI! I'll open an issue for that. |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Here are my operation steps:
docker run \ --name fief-server \ -p 8000:8000 \ -d \ -e "SECRET=XXX" \ -e "FIEF_CLIENT_ID=XXX" \ -e "FIEF_CLIENT_SECRET=XXX" \ -e "ENCRYPTION_KEY=XXX" \ -e "PORT=8000" \ -e "ROOT_DOMAIN=localhost:8000" \ -e "FIEF_DOMAIN=localhost:8000" \ -e "[email protected]" \ -e "FIEF_MAIN_USER_PASSWORD=XXX" \ -e "CSRF_COOKIE_SECURE=False" \ -e "SESSION_DATA_COOKIE_SECURE=False" \ -e "USER_LOCALE_COOKIE_SECURE=False" \ -e "LOGIN_SESSION_COOKIE_SECURE=False" \ -e "SESSION_COOKIE_SECURE=False" \ -e "FIEF_ADMIN_SESSION_COOKIE_SECURE=False" \ ghcr.io/fief-dev/fief:latest
Unfortunately, when I open the login page(http://localhost:8000/admin) in browser, something went run

So, I start to check the logs, found my password was too weak.

After re-running the docker start command, I get the correct feedback.
My confusion is that maybe we can enhance the password inputing part, so our users won't debug anymore when they have such problems.
Thank you.
Beta Was this translation helpful? Give feedback.
All reactions