Code

SKCE-ERR-1000

Message

Caught an exception\: {0}

Explanation

Generic message for when an exception is caught by the application. It is followed by the cause of the exception.

Code

SKCE-ERR-1003

Message

NULL or invalid argument\\: {0}

Explanation

Message indicating a null, empty or incompatible parameter.

Code

SKCE-ERR-1092

Message

SKCE Domain does not exist {0}

Explanation

Indicates the domain ID passed by the application does not exist.

Code

SKCE-ERR-1093

Message

SKCE Domain inactive

Explanation

Indicates that the domain ID passed by the application has been deactivated and cannot be used anymore.

Code

SKCE-ERR-1112

Message

Could not reload SKCE configuration\: {0}

Explanation

When the wizards reload configuration properties on the appliance; this error indicates the configurations could not be loaded successfully.

Code

SKCE-ERR-5001

Message

Signature not verified for db record; {0}

Explanation

Indicates the signature for the database records cannot be verified.

Code

SKCE-ERR-6000

Message

ZMQ Error\: {0}

Explanation

Generic ZeroMQ error followed by an error message.

Code

SKCE-ERR-6001

Message

ZMQ Publisher received an invalid object for publishing\: {0}

Explanation

Indicates the ZMQ publisher receives an invalid object for replication. This can only happen if the database entry for replication has been modified manually to include an invalid object.

Code

SKCE-ERR-6008

Message

ZMQ Subscriber received an unknown object\: {0}

Explanation

The ZMQ subscriber received an invalid object for replication. This can only happen if the database entry for replication has been modified manually to include an invalid object or it is trying to replicate a record for a schema the server does not understand.

Code

SKCE-ERR-6009

Message

ZMQ Subscriber could not parse replicated proto object\: {0}

Explanation

The ZMQ subscriber could not parse the Google Proto buffer object created for the object that is to be replicated.

Code

SKCE-ERR-6010

Message

ZMQ Subscriber received an invalid operation on a nonexistent object\: {0}

Explanation

This error occurs if ZMQ receives an operation which is not allowed on that object. Example: Updating a record that has not been added yet.

Code

SKCE-ERR-6011

Message

ZMQ Subscriber did not add replicated object to database—already exists locally\: {0}

Explanation

This error is generated when the object has already been replicated but the acknowledgment has not reached the original server, and it keeps trying to replicate it over and over again. Indicates that either the ZMQ acknowledger is broken or firewall rules between servers need to be fixed.

Code

SKCE-ERR-6012

Message

ZMQ Subscriber received an invalid operation\: {0}

Explanation

Occurs if ZMQ receives an operation which is not one of ADD | DELETE | UPDATE.

Code

SKCE-ERR-6014

Message

ZMQ BacklogProcessor cannot replicate object—did not find it in local database\: {0}

Explanation

This error is printed if the object that is being replicated has already been deleted and ZMQ backlog processor cannot find it.

Code

SKCE-ERR-6015

Message

ZMQ BacklogProcessor found an invalid object in Replication table for publishing\: {0}

Explanation

Indicates the ZMQ backlog processor found an object in the table that doesn’t belong.

Code

SKCE-ERR-6016

Message

ZMQ BacklogProcessor failed to push object\: {0}

Explanation

This is printed if ZMQ backlog processor cannot push an object followed by the error message.

Code

SKCE-ERR-6025

Message

ZMQ Subscriber did not delete object from database—object doesn't exist\: {0}

Explanation

This error is printed if ZMQ subscriber is trying to delete an object that has already been deleted. This can happen if replication is broken and backlog processor has already queued objects multiple times.

Code

SKCE-ERR-6094

Message

ZMQ Error\: Server is NOT Active—replication will NOT be started on {0}

Explanation

This message gets printed if there are server records in the database that are inactive.

Code

SKCE-ERR-6095

Message

ZMQ Error\: Server is NOT an Active Publisher—replication will NOT be started on {0}

Explanation

This message is printed if a specific server is not configured as a publisher.

Code

SKCE-ERR-6096

Message

ZMQ Error\: Server is NOT a Publisher—replication will NOT be started on {0}

Explanation

This message is printed if a specific server is not configured as a publisher.

Code

SKCE-ERR-6099

Message

ZMQ Error\: Server is NOT configured with a SID and/or FQDN—replication will NOT be started on {0}

Explanation

This error is printed if a server FQDN does not match the one configured in the database.

Code

SKCE-ERR-6090

Message

Object already persisted by another thread\: {0}

Explanation

This error is printed if two threads try to persist the same data.

Code

SKCEWS-ERR-3014

Message

NULL argument\: {0}

Explanation

This error indicates a null parameter followed by the name of the parameter.

Code

SKCEWS-ERR-3053

Message

Invalid argument\: {0}

Explanation

This error indicated invalid argument followed with the name of the parameter.

Code

SKCEWS-ERR-3055

Message

Invalid user: {0}

Explanation

This error indicates that the service credential used are invalid.

Code

FIDO-ERR-0001

Message

Caught an exception\: {0}

Explanation

Generic exception message. Followed by the actual error message.

Code

FIDO-ERR-0002

Message

Null or empty input\: {0}

Explanation

Message indicating a null or empty parameter.

Code

FIDO-ERR-0003

Message

Error during preregister\: {0}

Explanation

Indicates a generic error during preregister followed by the actual error message.

Code

FIDO-ERR-0004

Message

Input registrationresponse cannot be null or empty\: {0}

Explanation

Occurs when the registration response sent to the server is empty.

Code

FIDO-ERR-0005

Message

Input registration response does not contain needed fields\: {0}

Explanation

This message displays when the registration response does not have all the required fields, e.g., a missing clientdataJSON or missing ID.

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-0007

Message

No valid keys registered; please register first (could be db signature verification failure): {0}

Explanation

Authentication was attempted for an account with no registered keys.

Code

FIDO-ERR-0008

Message

Database access error\: {0}

Explanation

The server cannot access the database.

Code

FIDO-ERR-0009

Message

Error during preauth\: {0}

Explanation

A generic error during preauthenticate. Followed by the actual error message.

Code

FIDO-ERR-0010

Message

Input signresponse cannot be null or empty\: {0}

Explanation

Indicates when the authentication response sent to the server is empty.

Code

FIDO-ERR-0011

Message

Input signresponse does not contain needed fields\: {0}

Explanation

This is printed when authentication response does not have all the required fields, e.g., a missing clientdataJSON or missing ID.

Code

FIDO-ERR-0014

Message

JSON parsing exception\: {0}

Explanation

Generic exception printed if the input JSON is invalid.

Code

FIDO-ERR-0015

Message

User signature could not be verified\: {0}

Explanation

This error outputs if the attestation signature could not be verified with provided keys.

Code

FIDO-ERR-0016

Message

Registration metadata cannot be null\: {0}

Explanation

StrongKey FIDO Server requires the applications to provide some extra metadata related to user and location information during the registration operation.

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-0018

Message

Invalid registration metadata\: {0}

Explanation

StrongKey FIDO Server requires the applications to some extra metadata related to user and location information during registration operation. This is printed if reg_metadata is invalid.

Code

FIDO-ERR-0019

Message

Invalid request metadata\: {0}

Explanation

StrongKey FIDO Server requires the applications to some extra metadata related to user and location information during registration operation.

Code

FIDO-ERR-0020

Message

Invalid request parameters\: {0}

Explanation

This message outputs if the request has invalid parameters.

Code

FIDO-ERR-0021

Message

Request parameters cannot be null\: {0}

Explanation

Occurs if the request parameter is null or empty.

Code

FIDO-ERR-0022

Message

User key couldn't be fetched based on random ID; or it has been flushed away\: {0}

Explanation

This error is printed if the requested FIDO key information does not exist

Code

FIDO-ERR-0023

Message

Error deleting user key\: {0}

Explanation

Generic error during key deletion. Followed by an error message.

Code

FIDO-ERR-0024

Message

Error updating user LDAP attribute "FIDOKeysEnabled" to \: {0}

Explanation

LDAP cannot be updated during an update operation.

Code

FIDO-ERR-0025

Message

Failed to generate registration challenge \: {0}

Explanation

Generic error creating the preregister response. Followed by an error message.

Code

FIDO-ERR-0026

Message

Failed to update sign counter value\: {0}

Explanation

The server cannot update the Authenticator counter information.

Code

FIDO-ERR-0027

Message

Too long argument \: {0}

Explanation

An input parameter was longer than the allowed value.

Code

FIDO-ERR-0028

Message

Error deactivating user key\: {0}

Explanation

Generic error during key deactivation. Followed by an error message.

Code

FIDO-ERR-0029

Message

Error activating user key\: {0}

Explanation

Generic error during key activation. Followed by an error message.

Code

FIDO-ERR-0030

Message

Invalid Counter received.

Explanation

The Authenticator counter received has not incremented since the last authentication operation.

Code

FIDO-ERR-0031

Message

Invalid User Presence byte received.

Explanation

The user presence byte in the reg/auth response is invalid.

Code

FIDO-ERR-0032

Message

Appid-Origin mismatch.

Explanation

U2F protocol error that displays if the FIDO APPID-FACETID verification fails.

Code

FIDO-ERR-0033

Message

Authorization failed: Invalid service credentials

Explanation

The service credentials provided by the application are invalid.

Code

FIDO-ERR-0034

Message

DB Signature verification failed.

Explanation

The database record fails integrity verification.

Code

FIDO-ERR-0035

Message

The user is not authorized to perform this operation.

Explanation

The service credential is not authorized for FIDO operations.

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-0038

Message

Failed to parse FIDO policy.

Explanation

During start up, the server could not parse the policy configured in the database.

Code

FIDO-ERR-0041

Message

Invalid or missing "svcinfo" in request body.

Explanation

This message outputs 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 message outputs 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 message outputs 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 message outputs 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 message outputs 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 message outputs 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 message outputs 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 message outputs if the request has an invalid or missing "username" value in the request payload.

Code

FIDO-ERR-0049

Message

Invalid or missing "displayname" in request payload.

Explanation

This message outputs if the request has an invalid or missing "displayname" value in the request payload.

Code

FIDO-ERR-0050

Message

Invalid or missing "options" in request payload.

Explanation

This message outputs if the request has an invalid or missing "options" value in the request payload.

Code

FIDO-ERR-0051

Message

Invalid or missing "extensions" in request payload.

Explanation

This message outputs if the request has an invalid or missing "extensions" value in the request payload.

Code

FIDO-ERR-0052

Message

Invalid or missing "strongkeyMetadata" in request payload.

Explanation

This message outputs if the request has an invalid or missing "strongkeyMetadata" value in the request payload.

Code

FIDO-ERR-0053

Message

Invalid or missing "publicKeyCredential" in request payload.

Explanation

This message outputs if the request has an invalid or missing "publicKeyCredential" value in the request payload.

Code

FIDO-ERR-0054

Message

Invalid or missing "version" in request payload.

Explanation

This message outputs if the request has an invalid or missing "version" value in the request payload.

Code

FIDO-ERR-0055

Message

Invalid or missing "create_location" in request payload.

Explanation

This message outputs if the request has an invalid or missing "create_location" value in the request payload.

Code

FIDO-ERR-0056

Message

Invalid or missing "last_used_location" in request payload.

Explanation

This message outputs if the request has an invalid or missing "last_used_location" value in the request payload.

Code

FIDO-ERR-0057

Message

Invalid or missing "origin" in request payload.

Explanation

This message outputs if the request has an invalid or missing "origin" value in the request payload.

Code

FIDO-ERR-0058

Message

Invalid or missing "id" in request payload.

Explanation

This message outputs if the request has an invalid or missing "id" value in the request payload.

Code

FIDO-ERR-0059

Message

Invalid or missing "rawId" in request payload.

Explanation

This message outputs if the request has an invalid or missing "rawId" value in the request payload.

Code

FIDO-ERR-0060

Message

Invalid or missing "response" in request payload.

Explanation

This message outputs if the request has an invalid or missing "response" value in the request payload.

Code

FIDO-ERR-0061

Message

Invalid or missing "type" in request payload.

Explanation

This message outputs if the request has an invalid or missing "type" value in the request payload.

Code

FIDO-ERR-0062

Message

Invalid or missing "attestationObject" in request payload.

Explanation

This message outputs if the request has an invalid or missing "attestationObject" value in the request payload.

Code

FIDO-ERR-0063

Message

Invalid or missing "clientDataJSON" in request payload.

Explanation

This message outputs if the request has an invalid or missing "clientDataJSON" value in the request payload.

Code

FIDO-ERR-0064

Message

Invalid or missing "authenticatorData" in request payload.

Explanation

This message outputs if the request has an invalid or missing "authenticatorData" value in the request payload.

Code

FIDO-ERR-0065

Message

Invalid or missing "signature" in request payload.

Explanation

This message outputs if the request has an invalid or missing "signature" value in the request payload.

Code

FIDO-ERR-0066

Message

Invalid or missing "userHandle" in request payload.

Explanation

This message outputs if the request has an invalid or missing "userHandle" value in the request payload.

Code

FIDO-ERR-0067

Message

Invalid or missing "clientDataJSON" in request payload.

Explanation

This message outputs if the request has an invalid or missing "clientDataJSON" value in the request payload.

Code

FIDO-ERR-0068

Message

Invalid or missing "keyid" in request payload.

Explanation

This message outputs if the request has an invalid or missing "keyid" value in the request payload.

Code

FIDO-ERR-0069

Message

Invalid or missing "status" in request payload.

Explanation

This message outputs if the request has an invalid or missing "status" value in the request payload.

Code

FIDO-ERR-0070

Message

Invalid or missing "modify_location" in request payload.

Explanation

This message outputs if the request has an invalid or missing "modify_location" value in the request payload.

Code

FIDO-ERR-0071

Message

Invalid or missing "txid" in request payload.

Explanation

This message outputs 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 message outputs if the request has an invalid or missing "txpayload" value in the request payload.

Code

FIDO-ERR-0073

Message

Invalid or missing "usernames" in request payload.

Explanation

This message outputs if the request has an invalid or missing "usernames" value in the request payload.

Code

FIDO-ERR-0074

Message

Missing "saml" in payload's ssoRequest object

Explanation

This message outputs if the request has missing "saml" in the request payload.

Code

FIDO-ERR-0075

Message

Invalid "did" in request payload \: {0}

Explanation

This message outputs if the request has an invalid domain Id in the request payload

Code

FIDO-ERR-0076

Message

Invalid "protocol" in request payload

Explanation

This message outputs if the request has an invalid protocol in the request payload

Code

FIDO-ERR-0077

Message

Invalid "authtype" in request payload

Explanation

This message outputs if the request has an invalid authtype in the request payload

Code

FIDO-ERR-2001

Message

FIDO 2 Error Message \: {0}

Explanation

Generic error message. Followed by the actual error message

Code

FIDO-ERR-2002

Message

Unsupported Argument \: {0}

Explanation

An unsupported argument is passed by the application to the FIDO API.

Code

FIDO-ERR-2003

Message

Invalid svcinfo \: {0}

Explanation

Generic Message if there is invalid svcinfo in the request payload.

Code

FIDO-ERR-3010

Message

Policy for this domain does not allow this authenticator with the current status.

Explanation

Generic Message if the status of the authenticator is not valid.

Code

FIDO-ERR-3101

Message

Cross Origin verification failed. {0}

Explanation

This error occurs if the cross origin verification fails. Please refer the cross origin in the Policy Module.

Code

FIDO-ERR-5001

Message

Null or empty input\: {0}

Explanation

The input parameter sent is either null or empty.

Code

FIDO-ERR-5002

Message

Unsupported FIDO protocol version \:

Explanation

The application sent a FIDO protocol which is not U2F or FIDO2_0.

Code

FIDO-ERR-5003

Message

Session id could not be validated.

Explanation

The application sent a FIDO protocol which is not U2F or FIDO2_0.

Code

FIDO-ERR-5004

Message

Signature exception occurred \:

Explanation

Generic exception printed followed by the actual error for anything related to creating and verifying signatures

Code

FIDO-ERR-5005

Message

Failed to verify attestation signature \:

Explanation

FIDO2 Server failed to verify the attestation signature during FIDO registration.

Code

FIDO-ERR-5006

Message

Exception \: {0}

Explanation

Generic exception followed by the actual error message.

Code

FIDO-ERR-5008

Message

Un-supported key type \: {0}

Explanation

The attestation certificate used an unsupported key during U2F.

Code

FIDO-ERR-5009

Message

Public key in the attestation certificate is using an illegal curve \: {0}

Explanation

The attestation certificate used an invalid curve during U2F.

Code

FIDO-ERR-5010

Message

Un-supported or in-valid attestation certificate \: {0}

Explanation

The attestation certificate used an invalid curve during U2F.

Code

FIDO-ERR-5011

Message

JSON could not be parsed \: {0}

Explanation

Generic exception printed if the input JSON is invalid.

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-5013

Message

Error Base64 decoding Browserdata \: {0}

Explanation

The client data JSON returned during FIDO response is an invalid base64.

Code

FIDO-ERR-5014

Message

Invalid Request Type \: {0}

Explanation

The type of request is invalid.

Code

FIDO-ERR-5015

Message

Invalid challenge, Base64 decode failed \: {0}

Explanation

The challenge inside the clientdataJSON returned during the FIDO response is an invalid base64.

Code

FIDO-ERR-5016

Message

Base64 decode failed \: {0}

Explanation

Generic error if the base64 decoding fails for an input.

Code

FIDO-ERR-5017

Message

Invalid input \: {0}

Explanation

Generic error for an invalid input.

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-5019

Message

FIDO2 Policy Violation \: {0}

Explanation

Generic message to indicate if there is a policy violation for a domain.

Code

FIDOJPA-ERR-1001

Message

NULL argument\: {0}

Explanation

Generic error for a null argument. Followed by the parameter name.

Code

FIDOJPA-ERR-1002

Message

Invalid argument\: {0}

Explanation

Generic error for an invalid argument. Followed by the parameter name.

Code

FIDOJPA-ERR-1003

Message

Missing argument\:

Explanation

Generic error for a missing/empty argument. Followed by the parameter name.

Code

FIDOJPA-ERR-1004

Message

Not Implemented Yet\:

Explanation

Generic message to indicate methods that have not yet been implemented.

Code

FIDOJPA-ERR-2001

Message

Username and Key Handle combination exists.

Explanation

The keyhandle returned in the authentication response does not exist for the user.

Code

FIDOJPA-ERR-2002

Message

fkid does not exist.

Explanation

This is printed if the key with primary key (fkid) does not exist.

Code

FIDOJPA-ERR-2004

Message

DID and username combination exists.

Explanation

The username does not exist for the domain ID specified by the calling application.

Code

FIDOJPA-ERR-2005

Message

Policy does not exist. _

Explanation

This is printed if a FIDO policy does not exist for a domain.

Code

FIDOJPA-ERR-2006

Message

Unable to persist entry to database.

Explanation

Generic message if the server cannot persist a database entry.

Code

FIDO-ERR-1501

Message

 SKFS Domain does not exist {0}

Explanation

Generic message if the domain does not exist.

Code

FIDO-ERR-1502

Message

 SKFS Domain inactive

Explanation

Generic message if the domain is not active.

Code

FIDO-ERR-1601

Message

 Certificate already exists.

Explanation

Generic message if the certificate already exists.

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-7000

Message

 Please contact your Help Desk/Administrator with this code; this credential {0} cannot be used currently.

Explanation

Generic message if the credential can't be used for any reason like database manipulation etc

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.