Feature: Make strict password checking optional#8957
Merged
lstein merged 6 commits intoinvoke-ai:mainfrom Mar 10, 2026
Merged
Conversation
lstein
requested review from
JPPhoto,
Pfannkuchensack,
blessedcoolant and
dunkeroni
as code owners
github-actions
bot
added
api
python
…quirements - Add `strict_password_checking: bool = Field(default=False)` to InvokeAIAppConfig - Add `get_password_strength()` function to password_utils.py (returns weak/moderate/strong) - Add `strict_password_checking` field to SetupStatusResponse API endpoint - Update users_base.py and users_default.py to accept `strict_password_checking` param - Update auth.py router to pass config.strict_password_checking to all user service calls - Create shared frontend utility passwordUtils.ts for password strength validation - Update AdministratorSetup, UserProfile, UserManagement components to: - Fetch strict_password_checking from setup status endpoint - Show colored strength indicators (red/yellow/blue) in non-strict mode - Allow any non-empty password in non-strict mode - Maintain strict validation behavior when strict_password_checking=True - Update SetupStatusResponse type in auth.ts endpoint - Add passwordStrength and passwordHelperRelaxed translation keys to en.json - Add tests for new get_password_strength() function Co-authored-by: lstein <111189+lstein@users.noreply.github.com>
lstein
force-pushed
the
copilot/enhancement-relax-password-checking
branch
from
d351e1d to
0fd4038
Compare
Co-authored-by: lstein <111189+lstein@users.noreply.github.com>
…-relax-password-checking' into copilot/enhancement-relax-password-checking
JPPhoto
approved these changes
Mar 10, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
This PR adds a new
strict_password_checkingoption to theinvokeai.yamlconfiguration file that adjusts how password checking is performed in multiuser mode. When this option is absent orfalse, the system will accept any password, but will issue an advisory about the password strength:With
strict_password_checking: true, the former behavior is restored and the user must provide a password 8 characters or longer with a mixture of upper, lowercase and numbers.Password checking is now implemented on both the front and backend, so that if strict password checking is turned on, the user cannot work around it by calling an endpoint directly.
Related Issues / Discussions
See discord comments on the password requirements.
QA Instructions
multiuser: trueand strict_password_checkingabsent orfalse`strict_password_checking: trueininvokeai.yaml, restart, and verify weak passwords are blocked with an error message (existing behavior)Merge Plan
Simple merge
Checklist
What's Newcopy (if doing a release after this PR)