Notakey Two Factor extension

Users with enabled Notakey authentication provider will be sent authentication request to registered mobile device (phone, tablet) after entering a valid username and password. This plugin requires Wordpress Two-Factor plugin, that provides base authentication framework. After installing and configuring both plugins, an additional authentication provider will be added to provider list. To register a mobile device for Notakey authentication, use the "Two-Factor Options" section under "Users" → "Your Profile". Install "Notakey Authenticator" and scan provided QR code with Notakey app and enter required details for device registeration. Notakey authentication can be combined with other second factor authentication means: TOTP, email, backup codes and others. This plugin adds also some basic security policy options for Wordpress site admins:

• Enable Notakey 2FA provider for all users - enables Notakey authentication for all users (in case your users have devices already registered on other services).
• Allow users to provide onboarding details - lets users enter their mobile number, if SMS code verification onboarding is used.
• Reject user login without 2FA verification - blocks user login without any second factor authentication.

Other configuration options include:

• Various options to customize authentication request.
• Configuration for Notakey Authentication Server.

To adjust policy or configure this plugin, navigate to "Settings" → "Notakey MFA". Plugin requires a hosted or on-premise version of Notakey Authentication Server (yes, there is a free version) with configured service, onboarding requirements and API client credentials. See our documentation site for detailed instructions how to set up Notakey Authentication Server. API client setup The plugin talks to Notakey Authentication Server (NtkAS) over its REST API and authenticates with OAuth 2.0 client credentials. Register an API client (client ID and secret) using the Notakey Authentication Appliance configuration shell, then copy the values into "Settings" → "Notakey MFA" → "Authentication Server". The API client must be provisioned with at least the following scopes:

• urn:notakey:auth - create and query authentication requests.
• urn:notakey:user - look up service users and their registered devices.
• urn:notakey:usermanager - create, update and delete service users during device registration.

Additionally, urn:notakey:devicemanager is required if you want the plugin to be able to remove registered devices from a user account. Values required in the "Authentication Server" settings section:

• Service URL - address of your NtkAS instance, e.g. https://mfa.example.com.
• Client ID and Client Secret - API client credentials, found in the authentication server dashboard, "Access credentials" page.
• Service ID (Access ID) - service identifier from the authentication server dashboard service settings.
• Service Domain - domain announced to users, requires a DNS SRV record in that zone.

The plugin requests a bearer token from POST /api/token with grant_type=client_credentials and only the scopes needed for each call. You can verify credentials manually: curl -X POST https://mfa.example.com/api/token \ -d 'grant_type=client_credentials&client_id=&client_secret=&scope=urn:notakey:auth urn:notakey:user urn:notakey:usermanager' A successful response contains an access_token value. If the client is not provisioned with the requested scopes, the token request fails and the plugin will not be able to send authentication requests.

See the release history.