We're having the following situation when entering Talend Management Console. Since it was configured with an IdP (Entra ID, to be precise), at first, this was working as intended, logging through sso was successful. But, after a couple of weeks, we wanted to re enter the TMC with the same credentials, and now it's prompting the following error:
This user account has been deactivated. Please try again later or contact your administrator talend cloud sso.
Turns out, the account in the Entra ID App, is very much active, so is the user on Talend Cloud Console. So, we aren't able to log in to the console, neither disable the IdP button on the TMC from our tenant. All of the accounts have the security administrator role configured. However, none of these are able to log in.
If anyone has an idea how to solve this, we'll be very much grateful.
Thank you for reechoing out to the Qlik community,
The error message.
“This user account has been deactivated. Please try again later or contact your administrator”
is being created by Talend’s IAM (Identity & Access Management) service when the SSO authentication token is linked to a deactivated or mismatched account.
Likely Cause:-
The account session or SAML-linked identity in Talend’s system became invalidated or flagged as disabled, even though the Azure AD user and the Entra ID application are still active.
Talend does not refresh or re-link the user on login; it relies on previously stored data until manually updated or reset.
You can try the steps below:-
Create a temporary local admin in Talend Cloud Use Talend’s classic login (non-SSO) to add a secondary admin with full permissions. This bypasses the disabled SSO session.
Log in with that admin account Access the Talend Management Console (TMC) and go to Administration → Users.
Locate and “Reactivate” the SSO-linked user
Ensure the user shows as Active in Talend (not greyed out or disabled).
If needed, delete and re-provision the user so that the SAML assertion is re-linked properly.
Test SSO login again Attempt to sign in via SSO now that the account status is clean and synchronized.
If this is not helping, then you will need to get in touch with our internal support, as they will need to check some things from the backend.
