Social account association errors - ULM / DIM — SaaS Knowledge Center

These are the most common error cases and error codes returned by the Associate Social Account Process.

Invalid Credentials

If this Process is invoked without an authenticated user session, then the Process responds with a HTTP 400 status. The body includes a operationErrors array with the reason(s) as to what went wrong:

**RESPONSE - body**
{  
   operationErrors": {
      "code": "security-challenge-failed",
      "type": "com.uxpsystems.mint.framework.commons.exception.InsufficientPermissionException",
      "message": "Current user does not possess the correct authority to execute this ConnectProcess.",
      "authorities": [
         {
            "authority": "ROLE_ANONYMOUS"
         }
      ]
   }
}

`operationError`	Array of possible error objects. Each object describes a separate error condition.
`code`	An error object’s internal code name.
`type`	Internal reference of the operation error type.
`message`	Optional message that describes the error in a human readable format.
`authorities`	The list of authority roles currently granted to the user. Can be used to help supply context to authorization errors (e.g, a Process requires a user to be authenticated, but they are currently anonymous).

Error Codes

Below is a list of potential error codes that may be returned during the execution of this Process. Note: See Common Process Error Codes.

HTTP Status	Digital Identity Management Business Error Code	Description
`400`	`social-already-associated`	Social media is already associated with another Digital Identity Management User
`400`	`not-supported-provider`	Invalid social provider was specified.
`401`	`access-token-error`	Could not extract action token.

Parent topic:Associate Social Account to User Process