Password Policies

A password policy sets the rules every account password must satisfy — minimum length, character mix, reuse history, and how often a password must change. Strong policies are your first line of defense against credential-stuffing and brute-force attacks, so it's worth getting them right before you invite staff and customers onto the platform.

PeakCommerce delegates all authentication to Auth0, so password rules are enforced by Auth0 rather than stored inside PeakCommerce. Length, complexity, history, and expiration are configured during implementation to match your security requirements. Customers don't edit these directly in PeakCommerce unless they bring their own identity provider.

Policy levels

Auth0 offers predefined policies to choose from:

Policy	Requirements
None	No restrictions
Low	At least 8 characters
Fair	8+ characters, with upper- and lower-case letters and a digit
Good	Fair, plus a special character
Excellent	Good, plus no more than two identical characters in a row

Custom policies can add a higher minimum length (10+), required character types, password history (no reuse of recent passwords), expiration periods, a dictionary of common passwords to block, and exclusion of the user's personal data (name, email).

Multi-factor authentication

Because authentication runs through Auth0, you can layer multi-factor authentication (MFA) on top of any password policy. MFA enrollment status is read back into PeakCommerce per user, so administrators can confirm who has a second factor in place.

Who controls the policy

• PeakCommerce-managed (default) — your implementation team configures the Auth0 policy with you. We recommend Good or stronger as a minimum (or a custom policy); avoid None, Low, and Fair for production accounts.

• Your own IdP — connect your own identity provider and you keep full control of password and MFA policy within it.

To change your policy, contact your account team.

Related

• Session Management

• Single Sign-On for PeakCommerce Sites