1.1.2

• Ready for the WordPress.org plugin directory: every file refuses direct access, the login button's emblem is escaped where it is printed, tested up to WordPress 7.1.

1.1.1

• The REST API keeps refusing anonymous user lists on sites with plugins that hook the REST dispatch without returning its result (acf-to-rest-api).

Faable Auth for WordPress 1.1.0

• Users added in WordPress (Users → Add New) are created in Faable Auth with their password and role; role changes and deletions follow. Needs the Management API scopes create:users read:roles create:roles create:rolemembers delete:rolemembers on the site's client; without them the site keeps working and the user is flagged with a retry button.
• The REST API no longer lists the site's users to anonymous visitors (/wp-json/wp/v2/users). Signed-in users and Application Passwords are unaffected. To publish your authors on purpose: add_filter( 'faable_auth_restrict_rest_users', '__return_false' );
• User sync handles a tenant with two roles of the same name.

Install or update: download faable-auth.zip; sites with 1.0.0 get the update from WordPress → Plugins.

Faable Auth for WordPress 1.0.0

Sign in to WordPress with Faable Auth.

• Managed mode for sites hosted on Faable: the connection comes from the environment.
• Roles synced from Faable Auth; the user profile says "Managed by Faable Auth" and links to the user in the Faable dashboard.
• Settings page with links to the tenant in the Faable dashboard and to the documentation.
• Faable emblem on the login button, on a white disc.
• Local service users can keep Application Passwords for the REST API.

Install: download faable-auth.zip and upload it in Plugins → Add New → Upload Plugin. Docs: https://faable.com/docs/auth/integrations/wordpress