FIDO (Fast IDentity Online) is an open standard for online authentication. It is designed to solve the password problems stemming from a lot of security problems as we are suffering today.

Rather than relying on symmetric credentials (like passwords or PINs, typically which is a knowledge-based factor), FIDO is based on a public-key cryptography algorithm that is based on asymmetric credentials.

Simply, the device generates the key pair and stores the private key within the secure area, and sends the corresponding public key (as the name implies it is okay to be public) to the server.

Then, if the authentication is needed, the server sends challenges to the device and the device generates the digital signature with the private key and sends it to the server.

Finally, the server can validate the signature with the registered public key.

FIDO2 is an improved standard for use on the web and other platforms as well as mobile. Various web browsers and OS platforms currently support the FIDO2 standard API.

Basically, FIDO2 has the following operations - Registration, Authentication.

• The user is prompted to choose an available FIDO authenticator that matches the online service’s acceptance policy.
• User unlocks the FIDO authenticator using a fingerprint reader, a button on a second–factor device, securely–entered PIN, or other methods.
• The user’s device creates a new public/private key pair unique for the local device, online service, and user’s account.
• The public key is sent to the online service and associated with the user’s account. The private key and any information about the local authentication method (such as biometric measurements or templates) never leave the local device.

• Online service challenges the user to log in with a previously registered device that matches the service’s acceptance policy.
• User unlocks the FIDO authenticator using the same method as at Registration time.
• The device uses the user’s account identifier provided by the service to select the correct key and sign the service’s challenge.
• The client device sends the signed challenge back to the service, which verifies it with the stored public key and lets the user log in.

• server: FIDO2 server
• common: FIDO2 related common models
• rp-server: a simple RP server implementation
• spring-boot-stater: FIDO2 server wrapped in a spring boot starter

• Supported browsers (Supported authenticators and interfaces may be different depending on the current browsers implementations)
  • Chrome
  • Opera (inherited from Chrome)
  • Firefox
  • MS Edge (Windows 10 /w 2018 October Update)
  • MS Edge on Chromium
  • Safari
• Supported authenticators (Platforms and externals)
  • Any FIDO2 authenticators and U2F authenticators with None attestation
• Signature algorithms
  • RS1 (RSASSA-PKCS1-v1_5 w/ SHA-1)
  • RS256 (RSASSA-PKCS1-v1_5 w/ SHA-256)
  • RS384 (RSASSA-PKCS1-v1_5 w/ SHA-384)
  • RS512 (RSASSA-PKCS1-v1_5 w/ SHA-512)
  • PS256 (RSASSA-PSS w/ SHA-256)
  • PS384 (RSASSA-PSS w/ SHA-384)
  • PS512 (RSASSA-PSS w/ SHA-512)
  • EDDSA (EdDSA)
  • ES256 (ECDSA w/ SHA-256)
  • ES384 (ECDSA w/ SHA-384)
  • ES512 (ECDSA w/ SHA-512)
  • ES256K (ECDSA using P-256K and SHA-256)
• Supported attestation types
  • Basic
  • Self
  • Attestation CA (a.k.a Privacy CA)
  • None
  • Anonymization CA
• Supported attestation formats
  • Packed (FIDO2)
  • Tpm (Windows10 devices)
  • Android key attestation
  • Android SafetyNet (Any Android devices running 7+)
  • FIDO U2F (Legacy U2F authenticators)
  • Apple Anonymous
  • None
• Metadata service integration
  • FIDO MDSv2
• Supported extensions
  • credProps
  • credProtect

You need to run the FIDO2 server and RP Server first.

If you want to integrate your own RP Server, please implement APIs by referring to the sample codes. Regarding client sides, you may implement the web app for communicating with the RP server.

FIDO2 Server running on local environments uses h2 as an embedded DB. This needs to be replaced with commercial standalone DB for other environments such as staging, beta or real.

In the case of the local environment, you can use the h2 console. Add the following path /h2-console to the fido server URL to access the h2 web console.

e.g., http:https://localhost:8081/h2-console

We also provide our server in the form of a spring boot starter.

Check out the spring-boot-starter directory.

# Start RP Server
cd rpserver
./gradlew bootRun

# Start FIDO2 Server or Line-fido2-spring-boot Demo
cd server
./gradlew bootRun

cd spring-boot-starter/line-fido2-spring-boot-demo
./gradlew bootRun

• If data.sql doesn't work well in an IntelliJ environment, try commenting on this part in build.gradle.

jar {
  processResources {
    exclude("**/*.sql")
  }
}

This project utilizes Lombok to reduce implementing getter/setter/constructors. You need the Lombok plugin to build with IntelliJ and Eclipse. See the following web pages to get information.

https://projectlombok.org/