Interface OperationError.ClockSkewTooBig
- All Superinterfaces:
MobileAuthenticationClientError,OperationError
- Enclosing interface:
- OperationError
The clocks on the mobile and on the server are too apart and the server refused to validate the
JWS. You can ask the user to verify
that the device clock is correctly set.
This error can only occur when using a AuthorizationProvider.JwsAuthorizationProvider
with a Deregistration operation and during registration when the user already has an
authenticator registered.
-
Nested Class Summary
Nested classes/interfaces inherited from interface ch.nevis.mobile.sdk.api.operation.OperationError
OperationError.AppAttestationError, OperationError.ClockSkewTooBig, OperationError.DeviceProtectionError, OperationError.NetworkError, OperationError.NoDeviceLockError, OperationError.OperationNotSupportedByBackend, OperationError.ServerCanceledOperation, OperationError.SigningFailedWithStrongBox, OperationError.UserAlreadyRegisteredInAnotherServer, OperationError.UserNotRegisteredInServer -
Method Summary
Methods inherited from interface ch.nevis.mobile.sdk.api.MobileAuthenticationClientError
cause, descriptionMethods inherited from interface ch.nevis.mobile.sdk.api.operation.OperationError
errorCode
-
Method Details
-
server
The server where the error occurred.- Returns:
- the server where the error occurred
-
httpError
Returns the HTTP error used to identify a clock skew, if the skew was detected in an HTTP error response.Returns
Optional.empty()if the backend reports the clock skew directly in the body of a FIDO UAF message within a successful HTTP response.- Returns:
- an
Optionalcontaining the HTTP error, or an emptyOptionalif the skew was reported in a successful response
-