Skip to content

Existing username during user creation shows generic "User provisioning failed" error #3313

@Malith-19

Description

@Malith-19

Description

When a user attempts to register with a username that already exists in the system, the registration flow returns a generic User provisioning failed error (code FET-1022). The underlying cause logged server-side is an Attribute conflict, meaning the username is already taken — but this is not communicated clearly to the user.

The error message should instead inform the user that the username is already in use, so they can take corrective action without confusion.

Steps to Reproduce

  • Open the user creation form.
  • Enter a username that already exists in the system.
  • Submit the form.
  • Observe the error displayed: User provisioning failed.

API response

{
    "executionId": "019ebb83-86c7-7432-a7fc-3b68d19d6a37",
    "flowStatus": "ERROR",
    "data": {},
    "error": {
        "code": "FET-1022",
        "message": {
            "key": "flows.executor.errors.provisioning_failed",
            "defaultValue": "User provisioning failed"
        },
        "description": {
            "key": "flows.executor.errors.provisioning_failed_desc",
            "defaultValue": "An error occurred while provisioning the user"
        }
    }
}

Respective server logs

time=2026-06-12T16:38:10.331+05:30 level=ERROR msg="Failed to create user in the store" component=ProvisioningExecutor executorName=ProvisioningExecutor executionID=019ebb83-86c7-7432-a7fc-3b68d19d6a37 error="failed to create user in the store: Attribute conflict" trace_id=c22a6e1e-79e3-412d-a3e5-6c010cb56ba0

Version

0.44.0

Environment Details (with versions)

No response

Metadata

Metadata

Assignees

Type

No type
No fields configured for issues without a type.

Projects

No projects

Milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions