Teydea Login Security - Password Policy, Complexity Rules & Expiration
| 开发者 |
teydeastudio
bartoszgadomski |
|---|---|
| 更新时间 | 2026年8月28日 06:43 |
| PHP版本: | 7.4 及以上 |
| WordPress版本: | 7.1 |
| 版权: | GPLv3 |
| 版权网址: | 版权信息 |
详情介绍:
- Enforce password length and complexity rules from a single settings page.
- Set password expiration to ensure users update their passwords regularly.
- Require users to confirm their current password before making changes.
- Compatible with WordPress multisite networks.
安装:
- Upload the
password-requirementsdirectory to/wp-content/plugins/, or install the plugin through the WordPress plugins screen directly. - Activate the plugin through the "Plugins" menu in WordPress.
- Go to "Settings" > "Login Security" to configure your password policy.
- Enable the rules you need, adjust their settings, and save. Your password policy is now active.
屏幕截图:
常见问题:
How do I access the settings?
After activation, go to "Settings" > "Login Security" in the WordPress admin. The settings page lets you enable or disable individual rules and configure their values.
What happens when a user's password does not meet the policy?
On login, the user is redirected to the password reset form. On password change or registration, a clear error message explains which rules the password does not meet.
How are accented and non-Latin characters counted?
Length and unique-character rules count characters, not bytes. "hasło" counts as five characters, the same as any five-letter password written in plain ASCII. The consecutive-symbols limit for the username and display name is counted in characters too. One caveat: when an accent is typed as a separate combining mark rather than as a single accented character, the letter and the mark count as two characters.
Does this plugin work with WooCommerce?
WooCommerce integration is available in the PRO version. It enforces password policies on WooCommerce login, registration, checkout account creation (including Store API), account details, password change, and password reset forms. It also replaces WooCommerce's built-in password strength meter with your policy rules.
Does it work with LMS plugins like LifterLMS, Tutor LMS, LearnPress, or Sensei LMS?
Yes. The PRO version includes integrations for LifterLMS, Tutor LMS, LearnPress, and Sensei LMS. Password policies are enforced on registration, login, and password change forms within these plugins. See the integrations page for details.
Is the plugin compatible with WordPress multisite?
Yes. Teydea Login Security supports both standard WordPress installations and multisite networks.
Can I set different password rules for different user roles?
Yes, with the PRO version you can create multiple password policies and assign them to specific user roles or individual users.
What is the difference between the free and PRO versions?
The free version provides a single global password policy with length, complexity, age, restricted characters, restricted words and phrases, and current password requirements. The PRO version adds per-role and per-user policies, password reuse prevention, a blocklist of over 100,000 common passwords, breached password screening via HaveIBeenPwned, password expiry warning emails, vendor-default account detection, and integrations with WooCommerce, Ultimate Member, LifterLMS, Tutor LMS, LearnPress, Sensei LMS, BuddyPress, and bbPress. See the pricing page for details.
Where can I find the unminified source code?
All source ships with the plugin: the plugin's own JavaScript is in src/, and the bundled @teydeastudio/components and @teydeastudio/utils libraries are in deps/js/components/src/ and deps/js/utils/src/. To rebuild, install Node.js 20 and run npm install && npm run build in the plugin directory.
更新日志:
- Password policy hint is now shown wherever WordPress sets a password - on the Add New User, Profile and Edit User screens, in addition to the password reset form
- Passwords WordPress generates for new accounts now satisfy the active policy, so a user handed a generated password can sign in with it instead of being sent straight to a forced reset
- Fixed the consecutive user name symbols rule: the configured number is now the number of symbols allowed, matching the help text; a limit of 0 no longer rejects every password of a covered user; matching now ignores letter case; and a short password that is a slice of the user name is no longer let through
- Password length and uniqueness rules now count characters rather than bytes, so accented and non-Latin passwords are measured consistently. A password that met the minimum length on its byte count alone is no longer compliant, and the user will be asked to change it at their next login
- Restricted words and phrases, and the user name checks, now behave the same regardless of the server character encoding: entries and passwords are handled as UTF-8, malformed input is rejected on save and repaired on load, and a password containing undecodable characters can no longer slip past either check
- The minimum password age no longer blocks a password change the plugin itself compels, which could leave an account locked out between the two rules
- The password hint on the reset form now describes the account being reset rather than the visitor's own session
- The zero-limit warning under the consecutive symbols field is no longer shown for an inactive policy
- Accessibility: removed the external OWASP link from the password hint and the special characters help text, and fixed the label and help text associations across the settings screen form controls
- Markup moved out of translatable strings, so translators receive words only
- Password policies published through the Abilities API now carry a title and description for every field
- Compatibility with WordPress 7.1 confirmed
- Plugin assets and screenshots updated
- Dependencies updated
- Code improvements
- Security: fixed a privilege escalation vulnerability where a crafted request to the password reset form could assign any role, including Administrator, to an existing account. Exploiting it required a valid password reset link for an account the attacker already controls
- Fixed an error on sites running PHP 7.4 caused by PHP 8.0+ syntax in the password compliance check; PHP 7.4 compatibility is restored
- Fixed an issue on the login and password-change screens when another plugin passes an empty login message
- Dependencies updated
- Code improvements
- Security hardening: tightened REST error responses and policy-context role validation (defense-in-depth audit follow-up)
- New "Restricted words and phrases" list: define site-wide words and phrases that passwords may not contain, with a per-policy on/off toggle
- Settings page tabs are now reflected in the URL, so a tab can be bookmarked and shared
- Added a clear admin notice for unmet server requirements (minimum PHP/WordPress version, required extensions)
- Dependencies updated
- Code improvements
- Wording improvements re: "minimum unique characters" field
- Updated the notice behavior to display as "error" rather than a "message"
- Documented source code location in readme.txt (added FAQ entry)
- Dependencies updated
- Code improvements
- Compatibility with WordPress 7.0 confirmed
- Dependencies updated
- Formatting updates
- Code improvements
- Plugin icon and assets updated
- Security hardening - added missing escaping
- Dependencies updated
- Abilities API implemented: password policies are now available in WordPress MCP server
- Direct access protection added to all PHP files
- Dependencies updated
- Formatting updates
- Unnecessary translation files removed since these are loaded from WordPress.org
- Do not hardcode
wp-login.phppath for login form - Code improvements
- Support for restricting certain characters in passwords implemented
- Dependencies updated
- Code improvements
- Harden handling of the "allow_password_reset" filter to improve compatibility with third-party plugins
(For older records, see the
changelog.txtfile).