Product Documentation
- Release Notes
- Introduction
- Installation
- Administration
- Operations
- Security
- Operating System
- Policy
- SKFS Policy Module (PM)
- JSON Schema
- Minimal (Any Hardware Authenticator)
- Moderate (Specific Authenticators)
- Strict (All Biometric Devices)
- Strict (Android SafetyNet)
- Restricted (TPM)
- Restricted (Android)
- Restricted (Apple PassKey)
- Restricted (FIPS)
- MetaDataService (MDS)
- FIDO Policy Options
- Back
- Back
- Configuration
- CLI Tool
- SSO
- Back
- How To ...
- Troubleshooting
- Error Codes and Their Meanings
- Solutions for Known Issues
- RPID Hash invalid - Does not match policy
- Json could not be parsed : Policy requires counter
- Json could not be parsed : Invalid 'request type'
- mysql binary does not exist or cannot be executed
- Remote server does not listen for requests on [localhost:4848]
- CORS Missing Allow Origin or ERR_CERT_AUTHORITY_INVALID
- This security key doesn't look familiar. Please try a different one.
- JWT CIP 192.168.x.xx does not match: [localhost]]]
- Certificate not found in truststore while Authentication in StrongKey Discover
- Back
- Back
- Developer
- Sample Applications
- SKFS API
- REST API
- SOAP API
- API Security
- FIDO2-enabling a Web Application
- Back
- Build SKFS from source
- Tutorial
- Discoverable Credentials
- Back
- Demos
- MFA Implementations
SKFS contains a list of pairs of access and secret keys stored in a keystore file. In order to perform FIDO2 operations, the correct access and secret keys must be used by the servlet to talk to the FIDO2 Server.
In this example we will be using SKFS and PoC found at these URLs:
- https://sourceforge.net/projects/strongkeyfido/
- https://sourceforge.net/projects/strongkeyfido/files/v4.10.0/sampleapps/java/basic/
With SKFS and POC are both installed correctly, we may begin the process of creating new a new pair of access key and secret key.
Copyright (c) 2001-2024 StrongAuth, Inc. (dba StrongKey) All Rights Reserved