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 ...
- Perform SKFS Operations
- Manage SKFS Policy
- Manage SKFS Configuration
- Manage FIDO Metadata Service (MDS)
- Manage Keystores or Certificates
- Debug Replication Issues
- Create and add new alias
- Back
- Troubleshooting
- Verify if SKFS is functioning as expected
- 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
StrongKey FIDO Server (SKFS) has the ability to return with either a Json Web Token (JWT) or Security Assertion Markup Language (SAML) asserstion to be used for single sign on. These are configurable options in the SKFS and can be configured on a per site basis to include these with the authenticate response.
Copyright (c) 2001-2024 StrongAuth, Inc. (dba StrongKey) All Rights Reserved