CREATE DEMO USER should validate password against project password policy

[engalar]

Problem

When creating demo users via CREATE DEMO USER, mxcli does not validate the password against the project's password policy. The command succeeds, but the Mendix runtime silently fails to create the user on startup — no error or warning is logged.

The only symptom is Login FAILED: unknown user 'xxx' at login time, which is very misleading.

Steps to Reproduce

1. Set up a project with a strict password policy (e.g., min 12 chars, require digit, mixed case, symbol)
2. Create a demo user with a non-compliant password:

   CREATE DEMO USER 'testuser' PASSWORD '1' (User);

3. mxcli reports success: Created demo user: testuser
4. Run the app — the user is never created in the database
5. Login fails with unknown user 'testuser'

Expected Behavior

Either:

• Validate at creation time: mxcli reads the project's password policy and rejects non-compliant passwords with a clear error
• Warn at creation time: mxcli warns that the password may not meet the project's password policy

Environment

• mxcli version: latest
• Mendix version: 11.6.4
• Password policy: MinimumLength=12, RequireDigit=true, RequireMixedCase=true

[github-actions]

Issue Triage

Summary:
The CREATE DEMO USER command does not check the password against the project’s password policy, leading to a silent failure at runtime.

Checklist (bug report)

Required info	Present?	Details
mxcli version	❌	Only “latest” is given; need exact version/commit.
Mendix version	✅	11.6.4 provided.
Scenario	✅	Creating a demo user via CREATE DEMO USER in an MDL script/CLI command.
Expected output	✅	Validation or warning about non‑compliant password.
Experienced output	✅	Command reports success, but user isn’t created; login fails with “unknown user”.
AI bug report (diag bundle or session log)	❌	Not included.

What’s missing:

• The precise mxcli version (output of mxcli --version or commit/build identifier).
• A diagnostic bundle (mxcli diag --bundle) or at least the session log showing the command execution.

Could you please add those details? Thanks for reporting the issue!

---

Automated triage via OpenRouter — workflow source