Code |
SKCEWS-ERR-3055 |
Message |
Invalid user: {0} |
Explanation |
This error indicates that the service credential used is invalid. |
Code |
FIDO-ERR-0006 |
Message |
User session in-active\: {0} |
Explanation |
The user waited too long to click on the security key; the session timed out on the server side. In this case, session info is removed from the hash map. |
Code |
FIDO-ERR-0010 |
Message |
Input signresponse cannot be null or empty\: {0} |
Explanation |
This error is returned when the authentication response sent to the server is empty. |
Code |
FIDO-ERR-0014 |
Message |
JSON parsing exception\: {0} |
Explanation |
Generic exception printed if the input JSON is invalid. |
Code |
FIDO-ERR-0017 |
Message |
Authentication metadata cannot be null\: {0} |
Explanation |
StrongKey FIDO Server requires the applications to some extra metadata related to user and location information during registration operation. |
Code |
FIDO-ERR-0033 |
Message |
Authorization failed: Invalid service credentials |
Explanation |
The service credentials provided by the application are invalid. |
Code |
FIDO-ERR-0037 |
Message |
Invalid username in the FIDO metadata. |
Explanation |
The username sent in the metadata and the user for which the response is created do not match. |
Code |
FIDO-ERR-0041 |
Message |
Invalid or missing "svcinfo" in request body. |
Explanation |
This error code is returned if the request has an invalid or missing "svcinfo" value in the request body. |
Code |
FIDO-ERR-0042 |
Message |
Invalid or missing "did" in request svcinfo. |
Explanation |
This error code is returned if the request has an invalid or missing "did" value in the request svcinfo. |
Code |
FIDO-ERR-0043 |
Message |
Invalid or missing "protocol" in request svcinfo. |
Explanation |
This error code is returned if the request has an invalid or missing "protocol" value in the request svcinfo. |
Code |
FIDO-ERR-0044 |
Message |
Invalid or missing "authtype" in request svcinfo. |
Explanation |
This error code is returned if the request has an invalid or missing "authtype" value in the request svcinfo. |
Code |
FIDO-ERR-0045 |
Message |
Invalid or missing "svcusername" in request svcinfo. |
Explanation |
This error code is returned if the request has an invalid or missing "svcusername" value in the request svcinfo. |
Code |
FIDO-ERR-0046 |
Message |
Invalid or missing "svcpassword" in request svcinfo. |
Explanation |
This error code is returned if the request has an invalid or missing "svcpassword" value in the request svcinfo. |
Code |
FIDO-ERR-0047 |
Message |
Invalid or missing "payload" in request body. |
Explanation |
This error code is returned if the request has an invalid or missing "payload" value in the request body. |
Code |
FIDO-ERR-0048 |
Message |
Invalid or missing "username" in request payload. |
Explanation |
This error code is returned if the request has an invalid or missing "username" value in the request payload. |
Code |
FIDO-ERR-0050 |
Message |
Invalid or missing "options" in request payload. |
Explanation |
This error code is returned if the request has an invalid or missing "options" value in the request payload. |
Code |
FIDO-ERR-0071 |
Message |
Invalid or missing "txid" in request payload. |
Explanation |
This error code is returned if the request has an invalid or missing "txid" value in the request payload. |
Code |
FIDO-ERR-0072 |
Message |
Invalid or missing "txpayload" in request payload. |
Explanation |
This error code is returned if the request has an invalid or missing "txpayload" value in the request payload. |
Code |
FIDO-ERR-0075 |
Message |
Invalid "did" in request payload \: {0} |
Explanation |
This error code is returned if the request has an invalid domain ID in the request payload. |
Code |
FIDO-ERR-0076 |
Message |
Invalid "protocol" in request payload |
Explanation |
This error code is returned if the request has an invalid protocol in the request payload. |
Code |
FIDO-ERR-0077 |
Message |
Invalid "authtype" in request payload |
Explanation |
This error code is returned if the request has an invalid authtype in the request payload. |
Code |
FIDO-ERR-0081 |
Message |
Null or missing "quantity/page" in request payload |
Explanation |
This error code is returned if the request has null or missing quantity/page for getregisteredusers web service. |
Code |
FIDO-ERR-0082 |
Message |
Length of txpayload exceeds max characters |
Explanation |
This error is returned when the length of the txpayload input exceeds 10000 characters. |
Code |
FIDO-ERR-3101 |
Message |
Subdomain verification failed\: Web origin in client data does not match rpid in policy |
Explanation |
This error occurs if the subdomain verification fails. |
Code |
FIDO-ERR-5012 |
Message |
Fatal error: Challenge from browser data and authentication response do not match \: {0} |
Explanation |
This is printed if the challenge sent by server during “pre” calls does not match the ones returned in the response. |
Code |
FIDO-ERR-5018 |
Message |
No policy found for the domain |
Explanation |
Generic error when a policy is not configured for a domain. |
Code |
FIDO-ERR-5501 |
Message |
Missing 'id' |
Explanation |
This error is returned if the id is missing from the request body. |
Code |
FIDO-ERR-5502 |
Message |
Invalid 'id'; id cannot be base64 decoded\: {0} |
Explanation |
This error is returned if the id cannot be Base64 URL Decoded. |
Code |
FIDO-ERR-5503 |
Message |
Invalid 'id'; id != B64 URL-safe id\: {0} |
Explanation |
This error is returned if the id in the request body is not Base64 URL safe. |
Code |
FIDO-ERR-5504 |
Message |
Missing 'rawId' |
Explanation |
This error is returned if the rawId is missing from the request body. |
Code |
FIDO-ERR-5505 |
Message |
Invalid 'rawId'; rawId cannot be base64 decoded\: {0} |
Explanation |
This error is returned if the rawId cannot be Base64 URL decoded. |
Code |
FIDO-ERR-5506 |
Message |
Invalid 'rawId'; rawId != B64 URL-safe rawId\: {0} |
Explanation |
This error is returned if the rawId in the request body is not Base64 URL safe. |
Code |
FIDO-ERR-5507 |
Message |
Missing 'credential_type' |
Explanation |
This error is returned if the credential_type is missing from the request body. |
Code |
FIDO-ERR-5508 |
Message |
Invalid 'credential_type'\: {0} |
Explanation |
This error is returned if credential_type in the request body is not equal to "public-key". |
Code |
FIDO-ERR-5509 |
Message |
Missing 'clientData' |
Explanation |
This error is returned if the clientData is missing from the request body. |
Code |
FIDO-ERR-5510 |
Message |
Missing 'authenticationData' |
Explanation |
This error is returned if the authenticationData is missing from the request body. |
Code |
FIDO-ERR-5511 |
Message |
Invalid 'request type'\: {0} |
Explanation |
This error is returned if the request type is missing from the request body. |
Code |
FIDO-ERR-5512 |
Message |
Missing 'origin' in clientData |
Explanation |
This error is returned if the origin is missing from the request body. |
Code |
FIDO-ERR-5513 |
Message |
Missing 'client IP' |
Explanation |
This error is returned if the clientIp is null. |
Code |
FIDO-ERR-5514 |
Message |
Missing 'User-Agent' |
Explanation |
This error is returned if the user-agent is null. |
Code |
FIDO-ERR-5515 |
Message |
Missing 'origin' in MetaData |
Explanation |
This error is returned if the origin is missing from the request metadata. |
Code |
FIDO-ERR-5516 |
Message |
Missing 'authenticatorObject' |
Explanation |
This error is returned if the authenticatorObject is missing from the request body. |
Code |
FIDO-ERR-5517 |
Message |
Missing 'userHandle' |
Explanation |
This error is returned if the userHandle is missing from the request body. |
Code |
FIDO-ERR-5518 |
Message |
Missing 'signature' |
Explanation |
This error is returned if the signature is missing from the request body. |
Code |
FIDO-ERR-5519 |
Message |
Invalid 'authenticatorData'; authenticatorData cannot be base64 decoded\: {0} |
Explanation |
This error is returned if the authenticatorData cannot be Base64 decoded. |
Code |
FIDO-ERR-5520 |
Message |
Missing or invalid Authenticator Data |
Explanation |
This error is returned if the Authenticator Data cannot be decoded. |
Code |
FIDO-ERR-5521 |
Message |
Missing modifylocation in metadata |
Explanation |
This error is returned if the modifylocation is missing from the request metadata. |
Code |
FIDO-ERR-5522 |
Message |
Missing 'tokenBinding' |
Explanation |
This error is returned if the tokenBinding is missing from the request body. |
Code |
FIDO-ERR-5523 |
Message |
Invalid 'tokenBinding'\: {0} |
Explanation |
This error is returned if the token binding status is null, empty, or not one of three valid values: "present", "supported", or "not-supported". |
Code |
FIDO-ERR-5524 |
Message |
Missing username in metadata |
Explanation |
This error is returned if the username is missing from the request metadata. |
Code |
FIDO-ERR-5525 |
Message |
Invalid request parameter: txid |
Explanation |
This error is returned if the txid in the request does not match the txid found in the user session map. |
Code |
FIDO-ERR-5526 |
Message |
Invalid request parameter: txpayload |
Explanation |
This error is returned if the txpayload in the request does not match the txid found in the user session map. |
Code |
FIDO-ERR-5527 |
Message |
Authentication Signature verification failed |
Explanation |
This error is returned if the signature in the request body fails verification. |
Code |
FIDO-ERR-1602 |
Message |
Signature not verified for db record; {0} |
Explanation |
Generic message if the server is unable to verify the signature for the record. |
Code |
FIDO-ERR-7001 |
Message |
DB signature failed for this registered key ({0}). Please contact administrator for more details. |
Explanation |
This message occurs if the database verification fails for a registered key. |
Code |
FIDO-ERR-7002 |
Message |
Unable to retrieve FIDO key from database |
Explanation |
This error code is returned if there were no keys extracted from the database. |
Code |
FIDO-ERR-9001 |
Message |
ROR verification failed\: {0} |
Explanation |
This error code is returned if Related Origin Requests (ROR) verification fails. To learn more about ROR, please refer the release notes for SKFS v4.14.0. |