Who is this article for?

Users troubleshooting password entry.

Server access may be required to look at the logs for some steps.

This articles covers troubleshooting steps for password settings in Please Review (PR).

1. Native PR database or external system

First, check if users are logging in via a configured login source on the PR installation.

Sysadmin users can view and edit all login sources for any user, while admin users can only manage the login source they use themselves. Hence, sysadmins are preferable when multiple sources are involved.

In Admin, Users, search for the user and click Edit to see their login sources.

For multi-tenant setups, users must be found through their workgroup under Members – see Understanding the limitations of multi-tenant Please Review installations.

Users cannot reset a native PR password if they lack a native PR login.

If using external authentication, password resets must be done on that external system, not PR.

2. Password complexity

By default, native PR passwords require at least 6 characters. If changed to use regex, the PR application pool must be restarted to apply changes, logging out all users.

Test regex rules on sites like regex101.com if unsure.

Admins should provide clear messages about password complexity. Without this, users get generic errors and may need support to understand requirements, causing extra work.

Also verify if settings apply correctly and the app pool was restarted after changes. Regex101 helps clarify regex rules.

3. Password change frequency

If users are prompted to change passwords more or less often than PR settings specify, consider:

• What is the "Maximum password age" set in PR?
• Are they using native PR login or external authentication? PR settings only affect native logins.
• Is their browser auto-filling an old password?