mfaVerify(Credential)
AppDelegate.reachfive().mfaVerify( CredentialType, (1) code, authToken )
1 | This "CredentialType" should be either .Email or .PhoneNumber as shown in the examples below. |
Examples
import Reach5
AppDelegate.reachfive()
.mfaVerify(.Email,
authToken: profileAuthToken,
code: verificationCode)
.onSuccess{ _ in
// Do something
}
.onFailure { error in
// Return a ReachFive error
}
import Reach5
AppDelegate.reachfive()
.mfaVerify(.PhoneNumber,
authToken: profileAuthToken,
code: verificationCode)
.onSuccess{ _ in
// Do something
}
.onFailure { error in
// Return a ReachFive error
}
Parameters
Authorization token of the profile retrieved from login.
|
|||||||||||||
The credential type to verify. Values
|
|||||||||||||
The verification code sent by email or SMS. |
Response
Future<MfaCredentialItem, ReachFiveError>
MfaCredentialItem
friendlyName |
The name that is displayed by the system for the MFA credential item. |
createdAt |
The time when the MFA credential item was created. |
phoneNumber |
The phone number for the MFA credential. This is only applicable for the type |
email |
The email for the MFA credential. This is only applicable for the type |
type |
The MFA credential type.
|
ReachFiveError
Based on the problem, the ReachFiveError
will be:
-
AuthCanceled
: The user cancelled the request or no credential was available in the keychain. -
RequestError(apiError: ApiError)
for a Bad Request (status 400) error. -
AuthFailure(reason: String, apiError: ApiError?)
mainly for Unauthorized (status 401) error. -
TechnicalError(reason: String, apiError: ApiError?)
if it’s an Internal Server Error (status 500) or other internal errors.
ApiError
error |
The main error message. |
||||||
errorId |
The identifier of the error. |
||||||
errorUserMsg |
The user-friendly error message.
|
||||||
errorMessageKey |
The error message key. |
||||||
errorDescription |
The technical error message. |
||||||
errorDetails FieldError[] |
|