FIDO Universal 2nd Factor (U2F) is an open authentication standard that strengthens and simplifies two-factor authentication using specialized USB or NFC devices.
This document explains how to use the Gluu Server's included U2F interception script to implement a two-step, two-factor authentication (2FA) process with username / password as the first step, and any U2F device as the second step.
For more background on U2F, including a discussion of its security advantages, visit the Yubico blog.
- A Gluu Server (installation instructions);
- U2F interception script (included in the default Gluu Server distribution);
- At least one U2F device for testing, like one of the devices listed below.
- For Linux based operating system, a little modification required in udev rule, that is stated below.
Some well known U2F devices and manufacturers include:
The script has the following properties
|u2f_application_id||Unique Identifer, normally url of IDP||
|u2f_server_uri||URL of the oxAuth U2F server||
Follow the steps below to enable U2F authentication:
Manage Custom Scripts.
Click on the
Find the U2F script
Enable the script by checking the box
Scroll to the bottom of the page and click
Now U2F is an available authentication mechanism for your Gluu Server. This means that, using OpenID Connect
acr_values, applications can now request U2F authentication for users.
To make sure U2F has been enabled successfully, you can check your Gluu Server's OpenID Connect
configuration by navigating to the following URL:
"acr_values_supported": and you should see
Make U2F the Default#
If U2F should be the default authentication mechanism, follow these instructions:
Default Authentication Methodtab.
In the Default Authentication Method window you will see two options:
oxTrust acrsets the authentication mechanism for accessing the oxTrust dashboard GUI (only managers should have acccess to oxTrust).
Default acrsets the default authentication mechanism for accessing all applications that leverage your Gluu Server for authentication (unless otherwise specified).
If U2F should be the default authentication mechanism for all access, change both fields to U2F.
If U2F is set as a default authentication mechanism users will not be able to access the protected resource(s) while using a mobile device or a browser that does not support U2F (e.g. Internet Explorer).
U2F Login Page#
Below is an illustration of the Gluu Server's default U2F login page:
Using U2F Tokens#
U2F device enrollment happens during the first authentication attempt.
All subsequent U2F authentications for that user account will require the enrolled U2F key.
U2F Credential Management#
A users FIDO U2F devices can be removed by a Gluu administrator either via the oxTrust UI in
Manage People, or in LDAP under the user entry as shown in the below screenshot.
U2F Discovery Endpoint#
A discovery document for U2F is published by the Gluu Server at:
https://<hostname>/.well-known/fido-configuration This document specifies the URL of the registration and authentication endpoints. The endpoint was
https://<hostname>/.well-known/fido-2fa-configuration in previous versions, but has been deprecated in version 3.1.5.
U2F SCIM APIs#
For a discussion of how to manage FIDO devices using the SCIM protocol, see the SCIM documentation.
From your terminal run below commands and reboot your computer.
sudo curl https://hypersecu.com/downloads/files/configurations/70-u2f.rules > /etc/udev/rules.d/70-u2f.rules
chmod +x /etc/udev/rules.d/70-u2f.rules