Download the PHP package code-lts/u2f-php-server without Composer
On this page you can find all versions of the php package code-lts/u2f-php-server. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.
Download code-lts/u2f-php-server
More information about code-lts/u2f-php-server
Files in code-lts/u2f-php-server
Package u2f-php-server
Short Description Server side handling class for FIDO U2F registration and authentication
License BSD-2-Clause
Homepage https://github.com/code-lts/U2F-php-server#readme
Informations about the package u2f-php-server
U2F-php-server
Server-side handling of FIDO U2F registration and authentication for PHP.
Securing your online accounts and doing your bit to protect your data is extremely important and increasingly more so as hackers get more sophisticated. FIDO's U2F enables you to add a simple unobtrusive method of 2nd factor authentication, allowing users of your service and/or application to link a hardware key to their account.
Story about this library fork
All started in this issue in October 2020. I quickly worked hard on building tests and opening a pull-request. But nothing got merged because the library author vanished.
What does change in this fork ?
For the first released version: nothing changed, only tests where written. And PHP 8.1 support was done. Future versions may change things.
The Family of U2F php Libraries
Base Library
https://github.com/code-lts/U2F-php-server
Contents
- Installation
- Requirements
- OpenSSL
- Clientside Magic
- HTTPS and SSL
- Terminology
- Recommended Datastore Structure
- Process Workflow
- Registration Process Flow
- Authentication Process Flow
- Example Code
- Compatibility Check
- Registration Code
- Authentication Code
- Frameworks
- Laravel
- Yii
- CodeIgniter
- Licence
- Credits
Installation
composer require code-lts/u2f-php-server
Requirements
A few things you need to know before working with this:
- OpenSSL You need at least OpenSSL 1.0.0 or higher.
- Client-side Handling You need to be able to communicate with a some kind of device.
- A HTTPS URL This is very important, without HTTPS U2F simply will not work.
- A Datastore You need some kind of datastore for all your U2F registered users (although if you have a system with user authentication I'm presuming you've got this one sorted).
OpenSSL
This repository requires OpenSSL 1.0.0 or higher. For further details on installing OpenSSL please refer to the php manual.
Also see Compatibility Code, to check if you have the correct version of OpenSSL installed, and are unsure how else to check.
Client-side (The magic JavaScript Bit of talking with a USB device)
My presumption is that if you are looking to add U2F authentication to a php system, then you'll probably are also looking for some client-side handling. You've got a U2F enabled USB device and you want to get the USB device speaking with the browser and then with your server running php.
- Google already have this bit sorted : u2f-api.js
- Mastahyeti has created a repo dedicated to Google's JavaScript Client-side API : https://github.com/mastahyeti/u2f-api
HTTPS and SSL
For U2F to work your website/service must use a HTTPS URL. Without a HTTPS URL your code won't work, so get one for your localhost, get one for your production. https://letsencrypt.org/ Basically encrypt everything.
Terminology
HID : Human Interface Device, like A USB Device like these things
Recommended Datastore Structure
You don't need to follow this structure exactly, but you will need to associate your Registration data with a user. You'll also need to store the key handle, public key and the certificate, counter isn't 100% essential but it makes your application more secure.
Name | Type | Description |
---|---|---|
id | integer primary key | |
user_id | integer | |
key_handle | varchar(255) | |
public_key | varchar(255) | |
certificate | text | |
counter | integer |
TODO the descriptions
Process Workflow
Registration Process Flow
- User navigates to a 2nd factor authentication page in your application.
... TODO add the rest of the registration process flow ...
Authentication Process Flow
- User navigates to their login page as they usually would, submits username and password.
- Server received POST request authentication data, normal username + password validation occurs
- On successful authentication, the application checks 2nd factor authentication is required. We're going to presume it is, otherwise the user would just be logged in at this stage.
- Application gets the user's registered signatures from the application datastore:
$registrations
. - Application gets its ID, usually the domain the application is accessible from:
$appId
- Application makes a
U2F::makeAuthentication($registrations, $appId)
call, the method returns an array ofSignRequest
objects:$authenticationRequest
. - Application JSON encodes the array and passes the data to the view
- When the browser loads the page the JavaScript fires the
u2f.sign(authenticationRequest, function(data){ // Callback logic })
function - The view will use JavaScript / Browser to poll the host machine's ports for a FIDO U2F device
- Once the HID has been found the JavaScript / Browser will send the sign request with data.
- The HID will prompt the user to authorize the sign request
- On success the HID returns authentication data
- The JavaScript receives the HID's returned data and passes it to the server
- The application takes the returned data passes it to the
U2F::authenticate($authenticationRequest, $registrations, $authenticationResponse)
method - If the method returns a registration and doesn't throw an Exception, authentication is complete.
- Set the user's session, inform the user of the success, and redirect them.
Example Code
For a full working code example for this repository please see the dedicated example repository
You can also install it with the following:
- Compatibility Code
- Registration Code
- Step 1: Starting
- Step 2: Talking to the HID
- Step 3: Validation & Storage
- Authentication Code
- Step 1: Starting
- Step 2: Talking to the HID
- Step 3: Validation
Compatibility Code
You'll only ever need to use this method call once per installation and only in the context of debugging if the class is giving you unexpected errors. This method call will check your OpenSSL version and ensure it is at least 1.0.0 .
Registration Code
Registration Step 1:
Starting the registration process:
We assume that user has successfully authenticated and wishes to register.
Registration Step 2:
Client-side, Talking To The USB
Non-AJAX client-side registration of U2F key token. AJAX can of course be used in your application, but it is easier to demonstrate a linear process without AJAX and callbacks.
Registration Step 3:
Validation and Key Storage
This is the last stage of registration. Validate the registration response data against the original request data.
Authentication Code
Authentication Step 1:
Starting the authentication process:
We assume that user has successfully authenticated and has previously registered to use FIDO U2F.
Authentication Step 2:
Client-side, Talking To The USB
Non-AJAX client-side authentication of U2F key token. AJAX can of course be used in your application, but it is easier to demonstrate a linear process without AJAX and callbacks.
Authentication Step 3:
Validation
This is the last stage of authentication. Validate the authentication response data against the original request data.
Again, if you want to just download some example code to play with just install the full working code examples written for this repository please see the dedicated example repository
You can also install it with the following:
Licence
The repository is licensed under a BSD license. Read details here
Credits
This repo was originally based on the Yubico php-u2flib-server
All versions of u2f-php-server with dependencies
ext-openssl Version *