Best Option to migrate the Service Accounts to Client ID type authentication instead of User name and password with same name of Service Account and assign same roles. this was solving the problem in my case.
thanks
Jp.
------------------------------
Jayaprakash Kanagaraj
astrazeneca.com
------------------------------
Original Message:
Sent: 05-22-2025 12:56
From: Anonymous Member
Subject: Unable to assign workflow tasks to non-SSO user in the Local Workflow Adapter after MFA enforcement in Reltio
This message was posted by a user wishing to remain anonymous
Following is the issue that we are facing while assigning 'user_XYZ' (user name altered/masked for security concerns) to a workflow task in the local workflow adapter :-
While testing a custom workflow in the local workflow adapter and on trying to assign a workflow task to a valid non-SSO user "user_XYZ", the workflow task assignment API in Postman returns the error "Specified assignee [user_XYZ] is not a valid user" as depicted below:-
The user "user_XYZ" has MFA (Email) enabled and the workflow task assignment API call was made using the access token for this same user (access token API call made with the user's state token and TOTP received over email). Also please note that the user "user_XYZ" is already assigned the specific role required for assigning this specific workflow task.
Additionally I would like to mention that workflow tasks could be successfully assigned to the user "user_XYZ" before the MFA enforcement for non-SSO users was done in Reltio as shown below :-