CONNECTION_LOCKED
The data source indicated that the credentials provided were invalid.
http code 400
{
"error_category": "CONNECTION_ERROR",
"error_code": "CONNECTION_LOCKED",
"error_message": "The account is locked. prompt the user to visit the provider's site and unlock their account",
"display_message": "The given account has been locked by the provider. Please visit your provider's website to unlock your account."
}
Common causes
- The user entered their credentials incorrectly after more than 3-5 attempts, triggering the provider’s fraud protection systems and locking the user’s account.
Troubleshooting steps
- Request that the user log in directly to their provider. Attempting to log in is a reliable way of confirming whether the user’s account is legitimately locked with a given provider. If the user cannot log in due to their account being locked, the website will usually note it as such, giving supplemental information on what they can do to resolve their account.
- If the account is locked, ask the user to work with the provider to unlock their account. Steps on unlocking an account are usually provided when a login attempt fails with the provider directly, in the event that their account is actually locked. Once unlocked, they should then try to re-authenticate using Deck Link.
If the user is persistently locked out of their provider, submit an 'Invalid credentials errors' Support ticket with the following identifiers: access_token
, source_id
and link_token_id
.
Updated 3 months ago