/problems/mfa/factor-not-enrolled

This is a description of a specific error response that you can receive when using the INVERS OneAPI via REST.¹

Check out our API Basics to learn more about the basic structure of all error responses and to find out how you should handle them.

{
    "type": "/problems/mfa/factor-not-enrolled",
    "type_documentation": "https://developers.invers.com/problems/mfa/factor-not-enrolled",
    "title": "MFA factor not enrolled.",
    "status": 409,
    "detail": "The provided MFA factor type is not enrolled by the user.",
    "flow_id": "5e77e3e3-48ab-4955-8ab3-1c62339096ab"
}

Meaning

This problem type occurs when the Multi-Factor Authentication (MFA) method type provided in the header is not enrolled by the user.

Details

• Use the error response’s type property to handle specific errors and exception handling within your application. It’s comparable to an error code.
• The detail property contains additional, more human-readable information about the problem or error. This is explanatory text and you should not have any exception handling and error handling code depend on it, as it may change.

Detail examples

The following examples are typical texts which you might receive in the error response’s detail property. Note that it is not a complete list of all possible cases. Therefore expect to receive error responses with a detail property value not listed below.

The provided MFA factor type is not enrolled by the user.

The MFA factor you are trying to use in the MFA verification header is not enrolled for this account.

Possible solutions:

• Verify that you use a MFA method (such as email or authenticator app) which was activated for your account.

---

1. The flow_id is specific to each API call, so it will be different in your case. However, type, title and status will match your actual error response if you receive the error described on this page. ↩