Skip to main content

Identity error codes

144 Duplicate In Parameter Set

151 Invalid Parameter Value

152 Action Execution Failure

157 Invalid Request

186 Access Denied

187 Invalid Identity Token

238 Max User Api Key Limit Reached

239 API Key not found

657 User does not exist

The specified user does not exist

658 User already exists

A user with the specified identifier already exists

659 API Key display name already in use

There is already an active API Key with the specified display name

660 Role does not exist

The specified role does not exist

661 Role does not exist in identity provider

One or more of the roles specified do not exist in your identity provider (Okta)

662 Application does not exist

The specified application does not exist

663 Token does not exist

The specified domain token does not exist

679 Single Sign-on (SSO) Incorrectly Configured

This condition is encountered when the necessary configuration required to enable Single Sign-on (SSO) for your LUSID account is missing or not complete. To resolve this you will need to contact your LUSID administrator or LUSID Support to request that the correct configuration is applied.

680 Identity Provider Not Found

The specified identity provider does not exist

689 The supplied pagination token is invalid

692 This endpoint does not support impersonation

705 User In A Deleted State

706 User is not locked out

707 User is already activated

717 User's status is invalid for the given operation

718 User's status is invalid for resetting the user's password

719 User's status is invalid for expiring the user's password

784 Cannot update password

785 Incorrect authentication type for action

786 Action not valid for user of this type

787 Password validation failure

871 The specified impersonated user does not exist

939 Blocked by a Network Zone

943 Failure when querying Okta System Logs

2153 Invalid Authentication Token

2154 Invalid Identity Provider Access Token

2200 Tenant Scheduler Domain Job Error

-1 Unknown error

An unexpected error was encountered on our side.