To integrate adaptive event signing secured with FIDO-based event validation
1. Issue an event validation request with [](https://{tenant}.{environment}.tid.onespan.cloud/v1/users/{userID@domain}/generate-fido-authentication-request)[https://{tenant}.{environment}.tid.onespan.cloud/v1/users/{userID@domain}/events/validate](https://community.onespan.com/products/intelligent-adaptive-authentication/sandbox#/Events/eventValidationUsingPOST).
- Method: POST
- Payload:
- eventType
- cddc
- relationshipRef
- sessionID
- fidoAuthentication
- fidoProtocol: UAF11, FIDO2
- userVerification: required, preferred, discouraged (FIDO2 only) Can be null which will default to preferred.
- authenticationMessage (UAF only) Can be null.
- Response body:
- riskResponseCode: 14 (ChallengeFido)
- requestID
- sessionStatus: pending
- fidoAuthenticationRequest
2. After confirming the event data with the FIDO-based authenticator, issue a second event validation request with [](https://{tenant}.{environment}.tid.onespan.cloud/v1/users/{userID@domain}/generate-fido-authentication-request)[https://{tenant}.{environment}.tid.onespan.cloud/v1/users/{userID@domain}/events/validate](https://community.onespan.com/products/intelligent-adaptive-authentication/sandbox#/Events/eventValidationUsingPOST).
- Method: POST
- Payload:
- eventType
- cddc
- relationshipRef
- requestID
- sessionID
- credentials
- fidoAuthenticator
- authenticationResponse
- Response body:
- riskResponseCode: 0
- sessionStatus: accepted
- uafStatusCode For a full list of UAF status codes, refer to the [FIDO alliance documentation](https://fidoalliance.org/specs/fido-uaf-v1.0-ps-20141208/fido-uaf-client-api-transport-v1.0-ps-20141208.html). For FIDO2, this field will return null.