Authentication Errors
In this section, you will find the possible errors that may occur when trying to authenticate on the Unico IDCloud platform.
The errors returned in the request can be identified by the codes below and have the following structure:
1.0.1
Check if the ID provided in the formation of "iss" is the correct tenant ID given during the generation of the private key.
1.0.14
Check with the project manager if the application being used is active.
1.1.1
The "scope" parameter was not provided in the payload of the JWT used in the request.
1.2.4
The JWT used in the request has expired. Check the value specified in the "exp" field of the payload.
1.2.5
The JWT used in the request cannot be validated. Verify the parameters provided and ensure that it was signed correctly.
1.2.6
The private key used to sign the JWT in the request is no longer acceptable. Request new credentials for the account used.
1.2.7
The JWT used in the request is no longer acceptable as it has already been used. Generate a new token to make a new request.
1.2.11
The account used is not active.
1.2.14
The account used does not have the necessary permissions.
1.2.18
The account used has been temporarily locked due to exceeding the number of invalid authentication attempts.
1.2.19
The account used is not authorized to impersonate another user account (remove the "sub" parameter from the payload).
1.2.20 1.2.21
Failed to decode the JWT used in the request. Use a new token by including only the fields specified in the "Mandatory Fields" and "Additional Fields" sections, adhering to the naming, semantics, and type of each field.
1.2.22
The JWT used in the request contains additional fields in the payload that are not allowed. Use a new token by including only the fields specified in the "Mandatory Fields" and "Additional Fields" sections, adhering to the naming, semantics, and type of each field.
1.3.1
The account used has source IP restrictions.
1.3.2
The account used has access date/time restrictions.
Last updated
Was this helpful?