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
Upgrading SKFS Notes
As of SKFS version 4.6.0, the SKFS now uses JDK 11 instead of JDK 8. Because of this switch, a separate upgrade script has been created, while the old upgrade script has been renamed to specify its usage of JDK 8.
Before upgrading to the latest StrongKey FIDO Server version, servers running SKFS version < 4.5.0 must first upgrade to 4.5.0 using the upgrade-skfs-jdk8.sh script. Once the SKFS is running version 4.5.0, it will then be able to perform an upgrade to SKFS version 4.6.0+.
Copyright (c) 2001-2024 StrongAuth, Inc. (dba StrongKey) All Rights Reserved