Programmatically Adding & Disabling Users

We considered adding something like this for a long time but decided it was really tough to scale across all authentication providers. The core issues is there’s no consistent way to receive a message for a “deprovisioning” event.

For your specific case, I’d suggest a cron job with a script that:

• Uses WP-CLI to fetch all WordPress users https://developer.www.ads-software.com/cli/commands/user/list/
• Fetches all active users from your auth backend
• Do an array diff to find the WordPress users not in the auth backend and use WP-CLI to remove their role https://developer.www.ads-software.com/cli/commands/user/remove-role/ or delete them https://developer.www.ads-software.com/cli/commands/user/delete/

You might need to filter out some WordPress users that aren’t on the auth backend but shouldn’t be deleted.

One other option is to configure Authorizer to disable WordPress logins. This means folks can only log in if they have an active account on the backend. Downsides are you can’t log in if the auth backend goes down, and deprovisioned users who are still logged into WordPress will remain logged in until their WordPress login cookie expires.