Closed ayshsandu closed 4 days ago
I think the ideal fix here would be, to be able to add multiple conditions with AND/OR grouping to apply a workflow to a request. This will improve the filtering capability of workflow engagements. Fixing just claim update issue by providing some kind of configuration is a short sighted solution.
Rather applying to all claim updates, can't we use 'Advance' workflow applying policy which uses xpath?
This issue is being closed due to extended inactivity. Please feel free to reopen it if further attention is needed. Thank you for helping us keep the issue list relevant and focused!
Steps to reproduce:
Log in to the management console and add a workflow engagement for "User Claim Update Task"
Add a workflow definition which allows the user's in admin role can approve the task and associate it with the engagement created in step1
Login to the /dashboard and open "Account Recovery" Gadget and try to set answeres for the challenge questions and click update. Upon viewing the "Account Recovery" gadget again, we can observe that answers are not set. Instead of step3
In the console, the following error is printed,
I believe this behaviour should be available in previous product versions as well since we are using some user claims to store the challenge question answers. When the corresponding values are getting stored as claims, workflow gets engaged and operation become on-hold until an authorized user approves it. Hence, the challenge question update fails.
This behaviour might affect some other use cases as well that involves storing user management features related information in claims. Better to redesign the flow to accommodate to enable both of the above cases in the same server.