Get FIDO2 ceremony status
POST/nevisfido/fido2/status
Returns the status of a previously initiated FIDO2 ceremony.
Request
- application/json
Body
required
Responses
- 200
- 400
- 405
- 406
- 415
OK The server processed the request successfully. Check the response body for the FIDO2 status information.
- application/json
- Schema
- Example (from schema)
Schema
- Array [
- ]
Possible values: [tokenCreated, clientRegistering, clientAuthenticating, succeeded, failed, unknown]
Possible values: [1200, 1202, 1400, 1401, 1403, 1404, 1408, 1480, 1481, 1490, 1491, 1492, 1493, 1494, 1495, 1496, 1497, 1498, 1500]
Possible values: [0, 1, 2, 3, 4, 9, 11, 14, 15, 16, 17]
Possible values: [0, 1, 2, 3, 4, 5, 6, 7, 9, 12, 13, 14, 15, 16, 17, 255]
authenticators object[]
tokenInformation object
Possible values: [tokenRedeemed, tokenTimedOut]
dispatcherInformation object
{
"status": "tokenCreated",
"timestamp": "2024-07-29T15:51:28.071Z",
"userId": "string",
"uafStatusCode": 1200,
"asmStatusCode": 0,
"clientErrorCode": 0,
"authenticators": [
{
"aaid": "string",
"keyId": "string",
"extId": "string"
}
],
"tokenInformation": {
"dispatchTargetExtId": "string",
"tokenResult": "tokenRedeemed",
"dispatcherInformation": {
"name": "string",
"response": "string"
}
}
}
Bad Request The provided JSON payload does not match the defined structure in the Request Body section.
Method Not Allowed The method of the received request was not POST.
Not Acceptable The Accept header is not properly set to application/json.
Unsupported Media Type The Content-Type header is not properly set to application/json;charset=UTF-8.