PASSWORD_CLEAR_UNCONFIRMED

Cause

nextly users:clear-plaintext-passwords --apply was run without --confirm-default-hasher.

A custom passwordHasher passed to getNextly can store hashes that look like plain text to this command, and clearing them would lock those people out. So --apply also needs --confirm-default-hasher, your statement that no custom hasher ever wrote a stored password. Nothing was changed.

Fix

• Run nextly users:clear-plaintext-passwords without --apply to see how many accounts it would clear.
• If no custom passwordHasher was ever used, run nextly users:clear-plaintext-passwords --apply --confirm-default-hasher.

Example

✗ Nothing was changed: --apply also needs --confirm-default-hasher.
  Why:  --confirm-default-hasher is your statement that no stored password was written by a custom passwordHasher, now or earlier. A custom hasher's hashes can look like plain text here, and clearing them locks those people out.
  Next: If no custom passwordHasher ever wrote a password, run `nextly users:clear-plaintext-passwords --apply --confirm-default-hasher`.
  Docs: https://nextlyhq.com/docs/cli/errors/password-clear-unconfirmed  (PASSWORD_CLEAR_UNCONFIRMED)