Opens in a new tab
WordPress API credential security

Disable WordPress application passwords with precise control

Disable Application Passwords lets you close unused API credentials without blindly cutting off every integration. Restrict them by capability, role or individual password, then review, expire and revoke what already exists.

  • Disable for everyone, non-administrators or selected roles.
  • Switch individual credentials off without deleting them.
  • Block application-password use over XML-RPC and set inactivity expiry.
  • Review existing credentials and revoke them when necessary.
Disable Application PasswordsIllustrative settings preview
Quick answer

How do you disable application passwords in WordPress?

Enable Disable Application Passwords in TheOneWP's Components settings and choose who should lose application-password access: everyone, users below administrator level, selected roles or individual credentials. The module uses WordPress authentication filters to refuse those credentials. It does not delete existing passwords unless you explicitly revoke them, and it does not disable the REST API itself.

The forgotten credential problem

Another way in, outside the login form

Application passwords are separate credentials that let external tools authenticate to WordPress APIs. Useful when needed, easy to forget when not.

Normal login protections do not cover them

Application-password requests do not pass through the usual interactive login screen, so its second-factor flow and login-form protections are not applied to those credentials.

Disabling access is not the same as removing a secret

WordPress stores previously issued application passwords in user metadata. Refusing a password does not delete the underlying credential, which can work again if restrictions are lifted.

A single global rule can disrupt legitimate integrations

Some sites rely on API clients for publishing, automation or administration. Blocking every application password without reviewing those dependencies can disconnect tools that still need access.

Control without guesswork

Refuse what you do not need. Keep what you do.

Choose a scope that matches your site, see credentials that already exist and make revocation a conscious decision.

Close access you do not need

Refuse WordPress application passwords globally on sites that do not rely on external integrations.

Keep essential integrations connected

Use administrator, role or individual-password rules instead of forcing the same restriction onto every user.

Understand what is still active

Review existing credentials and revoke those you no longer trust or need, without confusing refusal with deletion.

Verified feature set

Flexible policy, visible credentials

These controls are present in the supplied module, its WordPress hooks and TheOneWP settings renderer.

Scope

Four distinct control modes

Choose Everybody, Everybody below administrator, The roles I choose or The passwords I choose.

All usersRolesPer credential
Inventory

A cross-user credential list

Inspect application passwords on accounts you may edit, with names, dates, last-use information and recorded IP addresses.

Credential inventoryAccount-level view
Restriction

REST-friendly XML-RPC controls

For passwords that remain allowed, independently refuse application-password authentication over XML-RPC.

XML-RPCREST API
Lifecycle

Inactivity-based expiry

Refuse an unused credential after a configurable number of days, including credentials never used after creation.

90 days default7–3650 days
Cleanup

Targeted or bulk revocation

Delete one credential, only currently refused credentials or all accessible credentials, using WordPress APIs.

Revoke oneRevoke refusedRevoke all
Accountability

Notifications and revoked-history notes

Optionally email another account owner after revocation, and retain a limited note when an owner removes a password.

Owner emailDeleted notes
Practical use cases

Right-sized protection for different sites

Whether you have no external integrations or several essential ones, the correct policy depends on what actually connects.

A site with no outside API clients

Choose Everybody to close application-password authentication for every user, including administrators, without disabling ordinary logins.

A team with trusted admin integrations

Choose Everybody below administrator or select individual roles, keeping necessary API access for users who genuinely require it.

Cleaning up legacy credentials

Inspect credentials, refuse individual passwords temporarily, then permanently revoke unused ones after confirming the integrations that relied on them.

Operational benefits

Make every credential a deliberate decision

Policy and cleanup stay separate, so you can investigate before making irreversible changes.

More than an on/off switchControl access globally, by capability, by WordPress role or per existing credential.
A clear inventorySee which editable accounts hold passwords and when they were last used.
Unused access stops workingOptional inactivity expiry refuses stale credentials on their next authentication attempt.
Revocation stays explicitDeleting a credential is a separate action, not a hidden side effect of enabling the module.
Performance behaviour

Authentication checks, not background scans

The module intervenes in WordPress credential checks. It does not continuously probe remote services.

Filters run at authentication time

Scope and expiry decisions are attached to WordPress application-password checks, where the user or presented credential is available.

Inventory is requested by the settings screen

The cross-user listing examines accounts with application-password metadata. It is not a front-end crawler or scheduled network task.

No invented speed promises

Per-request filter work is straightforward, but inventory cost depends on user and credential counts. No benchmark or performance gain is claimed.

Verified security implementation

Apply the rule where WordPress authenticates

Restrictions use WordPress's application-password hooks, while inventory and revocation use permission-checked admin requests.

01

Global and per-user availability filters

The Everybody scope refuses application-password availability site-wide. Narrower scopes use the per-user filter, preserving any earlier refusal made by other plugins.

02

Individual-password and inactivity checks

The authentication-error hook can reject a specific UUID or a credential whose last use, or creation date if never used, exceeds the configured inactivity period.

03

Nonce and capability checks for changes

AJAX inventory and revocation requests require a nonce and manage_options. Single-credential changes also check edit_user for the account, including on multisite.

04

Revocation through WordPress APIs

Permanent deletion uses WP_Application_Passwords::delete_application_password(), allowing WordPress's normal deletion hooks to run. Refused credentials are not silently destroyed.

Compatibility boundaries

Designed around WordPress authentication

The module restricts application-password credentials, not every possible way into WordPress.

WordPress core

REST API and XML-RPC application passwords

The module works through core application-password availability and authentication hooks. An XML-RPC option refuses this credential type specifically.

Core hooksAPI authentication
Roles

Role-aware and multi-role users

Selected roles are checked using the site's roles and the towp_user_roles filter, so an additional role can also trigger refusal.

Role restrictionsMulti Role
Multisite

Permission-aware visibility

The inventory and revoke operations only reach accounts the current administrator is allowed to edit, rather than assuming every network account is accessible.

edit_userUser metadata
Solution comparison

Granular controls versus a global off switch

Compare this verified module with the straightforward WordPress filter that disables application passwords for everyone.

CapabilityTheOneWP Disable Application PasswordsBasic global-disable snippet
Disable for all users Everybody scopeCan return false via the global WordPress availability filter
Preserve selected users Administrator, role and per-password modesRequires additional conditional code
Review existing credentials Cross-user inventory where permittedNot provided by that single filter
Expire inactive credentials Configurable inactivity periodNot provided by that single filter
Revoke credentials Single, refused-only or all-accessible revocationRequires a separate deletion workflow
Recommended workflow

Review, restrict and revoke in four steps

Protect API access without accidentally severing a publishing or automation integration that still depends on it.

01

Identify integrations first

Check which external tools currently use application passwords. Make sure you have another working way to manage the site before changing access.

02

Enable the module

Open TheOneWP's Components settings, switch on Disable Application Passwords and choose the required scope under Who loses them.

03

Review optional controls

For permitted users, set XML-RPC refusal or inactivity expiry. Inspect What exists right now to see saved credentials and any refused statuses.

04

Test before revoking

Verify that permitted integrations still authenticate and refused ones cannot. Then use Revoke application passwords only for credentials that should be permanently deleted.

Best practices

Be selective before being permanent

The settings are reversible. Deleted credentials are not, and integrations using them need replacement credentials.

01

Inventory dependencies before blocking access

Document which applications connect to WordPress and which user owns each credential. A global disable can interrupt those clients immediately.

02

Use the narrowest scope that meets the policy

Preserve legitimate administrator or role-specific access if an integration requires it. Use per-password switches to investigate individual credentials.

03

Distinguish expired, refused and revoked

Expired and refused passwords still exist in storage. A revoked password is deleted and must be replaced if the integration is still required.

04

Confirm changes with real API clients

Test an allowed and a refused application-password request. Confirm that the normal WordPress login remains available through its independent authentication path.

Common mistakes

Avoid three costly credential assumptions

Most surprises come from misunderstanding what a restricted application password does and does not do.

Assuming disabled means deleted

Turn the module off and refused credentials can work again. Revoke passwords you genuinely intend to remove, and update integrations accordingly.

Confusing XML-RPC credentials with the endpoint

The XML-RPC setting blocks application-password authentication through XML-RPC. It does not shut down XML-RPC or every authentication method.

Choosing roles without selecting any

In The roles I choose mode, leaving every role unchecked can mean no one is refused. The settings panel warns when a chosen scope currently blocks nothing.

Frequently asked questions

Disable Application Passwords FAQ

Answers based on the supplied TheOneWP module and its actual settings.

What does Disable Application Passwords do?

It lets you refuse WordPress application passwords for everyone, for users without administrator-level permissions, for selected roles or one credential at a time. It also adds optional XML-RPC, inactivity-expiry and revocation controls.

Does disabling an application password delete it?

No. Refused credentials remain in WordPress user metadata and can start working again when the settings allow them. Use Revoke to delete a credential permanently.

Can administrators keep their application passwords?

Yes. Choose Everybody below administrator. The module checks the manage_options capability, so users with that capability retain access even if their role is not literally named Administrator.

Can I block application passwords for specific WordPress roles?

Yes. Choose The roles I choose, then enable the roles you want to refuse. When a user has multiple roles, a selected role is enough for the restriction to apply.

Can I disable just one application password?

Yes. Choose The passwords I choose and use the switch beside an existing credential. Switching it off refuses authentication without deleting it; turning it back on allows it again, unless another rule blocks it.

Does it disable the WordPress REST API?

No. It controls authentication through application passwords, not the REST API itself. REST endpoints and other permitted authentication methods are separate concerns.

Does it shut down XML-RPC completely?

No. Refuse them over XML-RPC blocks application-password authentication over that interface while allowed credentials can still work for REST requests. The separate Disable XML-RPC module can close the endpoint itself.

Can unused application passwords expire automatically?

Yes. Turn on Expire the ones nobody uses and choose an inactivity period, from 7 to 3650 days. The default setting is 90 days. An expired credential is refused when used, not deleted.

Can I see existing credentials across user accounts?

The settings panel lists credentials for accounts you have permission to edit, including the owner, creation time, last use and last recorded IP address when available. On multisite, it does not expose accounts you cannot edit.

Can I revoke only credentials that are currently refused?

Yes. The revoke dialog offers deletion of currently refused credentials or all visible, editable-account credentials. Revocation is permanent and is separate from simply disabling them.

Will users be emailed when their application passwords are revoked?

Optionally. Email the owner when a password is revoked sends a notice when an administrator revokes someone else’s credential. It does not send that notice when a user revokes their own.

Does this replace two-factor authentication or a firewall?

No. WordPress application-password authentication bypasses the regular interactive login form. This module restricts those credentials; separate protections are still needed for other login and API risks.

Keep the integrations you trust.Refuse the credentials you do not.

Control WordPress application-password access, inspect existing credentials and revoke unused secrets with deliberate, transparent choices.