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
Before upgrading to SKFS 4.12.0, if you are running a SKFS version lower than 4.10.0, make sure to upgrade to SKFS 4.10.0 first using the upgrade-skfs.sh script from the 4.10.0 distribution. Once you have successfully upgraded to SKFS 4.10.0, you may continue to upgrade to SKFS 4.12.0 using the new upgrade-skfs.sh script.
This SKFS 4.12.0 upgrade does not include any configurable property changes. Simply run the upgrade script.
Copyright (c) 2001-2024 StrongAuth, Inc. (dba StrongKey) All Rights Reserved