Register a new user
POST/useractions-srv/registration
To register a user, provide all mandatory and optional information (e.g., family_name, mobile_number) as defined in app settings.
The system checks if preferred fields are enabled in field setup. Disabled fields are skipped during registration.
Public registration call. Send the requestId header. No bearer token is required. The app for that requestId must allow cidaas:register, or allow cidaas:invite when invite_id is sent.
Password policy and compromised passwords
If the app password policy has compromised-credential blocking enabled, registration rejects passwords found in known breach databases. Treat HTTP 400 with code 10265 (password is compromised) as a validation error: ask the user to choose a different password and retry. See Password Policy and Compromised Credentials Detection.
Scenario: cidaas:invite
When users are invited via Admin UI, invite_id is passed in the payload. This value is embedded in the invite shortener link sent via email. Users fill in required fields as configured in app settings.
Scenario: cidaas:register
Register users directly by entering their email_id, mobile, or any identifier. Users provide necessary fields as defined in app settings.
Request
Responses
- 200
- 400
- 409
OK
Bad Request
Conflict