Currently, we have identified that some changes made to chrome u2f extension is causing the Fido device to not register properly as an authentication factor. Moreover, Firefox also does not support the u2f extension anymore.
We are in the process of fixing this issue using WebAuthn API which is already supported by the latest versions of Chrome(CHROME 67), Firefox (FIREFOX 60) & Edge browsers (EDGE 17723). Till then we recommend you to disable FIDO temporarily while we fix this issue.
The following topics provide details and instructions on how to configure multi-factor authentication (MFA) using the WSO2 Identity Server. This topic expands on what MFA is and how it can be used in certain scenarios. It also provides information on FIDO and how MFA can be configured using FIDO U2F.
The Fast IDentity Online (FIDO) attempts to change the nature of authentication by developing specifications that define an open, scalable, interoperable set of mechanisms that supplant reliance on passwords to securely authenticate users of online services. In short, FIDO U2F (Universal 2nd Factor) can make it easy for you to authenticate users while also ensuring that security is enhanced.
FIDO provides two user experiences to address a wide range of use cases and deployment scenarios. FIDO protocols are based on public key cryptography and are strongly resistant to phishing.
Figure 1: UAF and U2F
Universal Authentication Framework (UAF)
UAF involves a password-less experience with the following key processes:
The user carries the client device with the UAF stack installed.
The user presents a local biometric or PIN.
The website can choose whether to retain the password.
Universal Second Factor (U2F)
U2F focuses on the 2nd-factor experience and has the following key processes:
- The user carries the U2F device with built-in support in web browsers.
- The user presents the U2F device.
- The website can simplify the password (for example, it can be simplified to a 4-digit PIN).
U2F tokens provide cryptographic assertions that can be verified by relying parties. Typically, the relying party is a web server, and the cryptographic assertions are used as second-factor (in addition to passwords) during user authentication. U2F tokens are typically small special-purpose devices and FIDO Client is a web browser communicate between token and relying party.
U2F protocol operations
The following are the two main processes that take place when using FIDO U2F:
- Registration: Upon registration, a device gives the server its attestation certificate. This certificate can be (optionally) used to verify the authenticity of the device.
- Authentication: The authentication operation proves possession of a previously-registered keypair to the relying party.
Both the registration and authentication operation consists of three phases depicted in the following figure.
Figure 2: Three phases of U2F protocol operations
- Setup: In this phase, the FIDO Client contacts the relying party and obtains a challenge. Using the challenge (and possibly other data obtained from the relying party and/or prepared by the FIDO Client itself), the FIDO Client prepares a request message for the U2F token.
- Processing: In this phase, the FIDO Client sends the request message to the token, and the token performs some cryptographic operations on the message, creating a response message. This response message is sent to the FIDO Client.
- Verification: In this phase, the FIDO Client transmits the token's response message, along with other data necessary for the relying party to verify the token response, to the relying party. The relying party then processes the token response and verifies its accuracy. A correct registration response will cause the relying party to register a new public key for a user, while a correct authentication response will cause the relying party to accept that the client is in possession of the corresponding private key.
Basic authentication process flow of U2F
The following figure provides the complete authentication process flow when authenticating using FIDO U2F.
Figure 3: Authentication process flow for U2F
Configuring multi-factor authentication using FIDO
The instructions in this section enable you to successfully set up multi-factor authentication using the WSO2 Identity Server.
FIDO authenticator can be configured only after a local authenticator is configured in the previous steps. It cannot be configured as the 1st step or if federated authenticator set the subject identifier.
Setting up an account for MFA
- Log in to the WSO2 Identity Server end-user dashboard.
- Navigate to the My Profile section by clicking the associated View Details button.
Click Manage U2F Authentication.
When you click this, the FIDO device that you need to add must already be plugged into the computer.
You can add a new U2F device to your account and remove it if needed. The new U2F device can be added by clicking the Attach FIDO Token button. Then you need to touch the 'key' icon on the FIDO device in order to complete the adding process. Once you have added the devices, they are listed on the page that appears. By clicking the Remove button, you can remove any device you want.
You can have multiple devices associated with your account.
Configuring FIDO U2F as an authenticator
- Log in to the Management Console.
- Navigate to the Main menu to access the Identity menu. Click Add under Service Providers.
Create a new Service Provider:
For more information on creating a service provider, see Adding and Configuring a Service Provider.
- Fill in the Service Provider Name and provide a brief Description of the service provider. Only Service Provider Name is a required field.
- Click Register to add the new service provider.
Access the service provider you just created and expand Local & Outbound Authentication Configuration.
For more information on configuring the local and outbound authentication configuration, see Configuring Local and Outbound Authentication for a Service Provider.
- Select Advanced Configuration to configure multi-factor authentication.
- Click Add Authentication Step. Then add a local authenticator from Local Authenticators section.
Select "Use subject identifier from this step" and "Use attributes from this step" options from this step since we identify the user from this step.
- Click Add Authentication step and add FIDO authenticator from Local Authenticators section. This will enable the FIDO as the 2nd step authenticator for the users who authenticated with the basic authentication.
- Click the Update button. This navigates you to the previous screen with your newly configured authentication steps.
Checking browser support for FIDO devices
The https://demo.yubico.com/u2f site can be used to check the browser support for FIDO devices.
As for now, Google Chrome (version 38 or later) has support for FIDO devices. Firefox does not support FIDO natively. An add-on must be added to Firefox to support FIDO devices. You can download and install the add-on from here.