- 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 ...
- Add an Additional Server to the SKFS Cluster
- Create and add new alias
- Debug Replication Issues
- Manage FIDO Metadata Service (MDS)
- Manage Keystores or Certificates
- Manage SKFS Policy
- Manage SKFS Configuration
- Perform SKFS Operations
- Replace a Server in the SKFS Cluster
- Back
- Troubleshooting
- Standalone Node Troubleshooting Guide
- Clustered Node Troubleshooting Guide
- Error Codes and Their Meanings
- Solutions for Known Issues
- Certificate not found in truststore while Authentication in Discover
- CORS Missing Allow Origin or ERR_CERT_AUTHORITY_INVALID
- Json could not be parsed : Invalid 'request type'
- Json could not be parsed : Policy requires counter
- JWT CIP 192.168.x.xx does not match: [localhost]]]
- mysql binary does not exist or cannot be executed
- Remote server does not listen for requests on [localhost:4848]
- RPID Hash invalid - Does not match policy
- This security key doesn't look familiar. Please try a different one.
- 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
To allow applications to enable end users to manage their registered FIDO credentials at RP sites, SKFS provides the getuserkeys operation to retrieve registered credentials for multiple users from SKFS, so the application can provide appropriate user experience (UX) to support user-managed operations.
The web service requires the following parameters supplied as JSON objects (shown in the Request example in this section):
|
Value |
Explanation |
|---|---|
|
svcinfo |
Every web service request sent by applications to SKFS must be authenticated and authorized. These privileges are based on service credential information (svcinfo) passed into the web service as a JSON object |
|
payload |
This parameter, also a JSON object, carries information about the list of usernames for which the registered keys should be fetched |
Copyright (c) 2001-2024 StrongAuth, Inc. (dba StrongKey) All Rights Reserved