UX: Exception from server not visible in front-end

UX
1

In release 2024.9 a new handling of exceptions was introduced and stack trace in responses was reduced.

I have come across a case where the exception from the method IdentityService.CreateUser isn’t returned even though it is vital information for the user. Instead of being informed about the problem they get There was an error, check log for details.

2025-03-04 10:06:46,848 [5] ERROR Origam.Workflow.WorkflowEngine - Passwords must have at least one non alphanumeric character.
Workflow stack trace
	Step: '30_trans/25_set_CreateOrigamUser'
	Step: '30_trans/30_CreateUser_Membership'

Origam.OrigamException: Passwords must have at least one non alphanumeric character.
 ---> System.Exception: Passwords must have at least one non alphanumeric character.
   at Origam.Security.Identity.IdentityServiceAgent.CreateUser() in D:\a\1\s\backend\Origam.Security.Identity\IdentityServiceAgent.cs:line 623
   at Origam.Security.Identity.IdentityServiceAgent.Run() in D:\a\1\s\backend\Origam.Security.Identity\IdentityServiceAgent.cs:line 93
   at Origam.Workflow.Tasks.ServiceMethodCallEngineTask.OnExecute() in D:\a\1\s\backend\Origam.Workflow\Tasks\ServiceMethodCallEngineTask.cs:line 200
   at Origam.Workflow.ProfilingTools.<>c__DisplayClass4_0.<ExecuteAndLogDuration>g__FuncToExecute|0() in D:\a\1\s\backend\Origam.Workflow\ProfilingTools.cs:line 63
   at Origam.Workflow.ProfilingTools.ExecuteAndLogDuration(Func`1 funcToExecute, String logEntryType, String path, String id, Func`1 logOnlyIf) in D:\a\1\s\backend\Origam.Workflow\ProfilingTools.cs:line 97
   at Origam.Workflow.ProfilingTools.ExecuteAndLogDuration(Action action, String logEntryType, String path, String id, Func`1 logOnlyIf) in D:\a\1\s\backend\Origam.Workflow\ProfilingTools.cs:line 66
   at Origam.Workflow.Tasks.AbstractWorkflowEngineTask.MeasuredExecution() in D:\a\1\s\backend\Origam.Workflow\Tasks\AbstractWorkflowEngineTask.cs:line 99
   at Origam.Workflow.Tasks.ServiceMethodCallEngineTask.Execute() in D:\a\1\s\backend\Origam.Workflow\Tasks\ServiceMethodCallEngineTask.cs:line 66
   --- End of inner exception stack trace ---

Another issue is that the error message isn’t a well formed json, so it isn’t processed and shown to the user.

image
image497×113 3.32 KB

4

I cannot reproduce this in master. @washi in what versions do we want to fix this?

5

If a fix is needed, it should go to master branch.

6

@zcapkova in what version does this occur?

7

Origam version: 2025.3.0.3752

8
9