Token dispatch endpoint
POST/nevisfido/token/dispatch/authentication
This is a proprietary nevisFIDO API — not part of the FIDO UAF standard — used to generate and dispatch an operation token to a registered dispatch target, triggering a FIDO UAF registration, authentication, or deregistration flow on a remote device.
The request body follows the GetUAFRequest structure defined in the FIDO UAF HTTP Transport Specification, specifying the operation type and optionally the target user and dispatch destination.
nevisFIDO generates the token, dispatches it via the configured dispatcher (such as an FCM push notification service), and returns a DispatchTokenResponse containing the dispatch outcome and the token itself for channel binding.
Note that HTTP 200 is always returned for a well-formed request — the dispatchResult field in the response body indicates whether the token was successfully dispatched or an error occurred.
Request
Responses
- 200
- 400
- 401
- 405
- 406
- 415
- 500
OK The server processed the request. A DispatchTokenResponse is returned. Note that HTTP 200 does not guarantee successful dispatch — check the dispatchResult field for the actual outcome.
Bad Request The provided payload is not properly formatted.
Unauthorized The request was not authorized. There is an invalid SecToken or unresolved username.
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.
Internal Server Error The server could not process the request because of an unexpected error.