How Custom User Validation Works

The following steps detail how you can use custom logic to authenticate end-user sign ups:

Note: Public Signup must be enabled to use Custom User Validation.
  1. When an end-user signs up to your application using the Sign Up action configured by you, the Catalyst server will check if Custom User Validation has been enabled. If it has been enabled, then the Basic I/O function that you have used to engineer the validation logic will be called and the user details will be passed to the validation function as a .JSON object.
{ "request_type": "add_user", "request_details": { "user_details": { "email_id": "", "first_name": "Emma", "last_name": "Thompson", "org_id": "43************", "role_details": { "role_name": "App User", "role_id": "10********" } }, "auth_type": "web" } }
  • Custom User Validation only applies for sign up action, i.e., when the user tries to access your Catalyst application for the very first time.

  • If you wish to alter any one of the input details for validation, the input to the function has to be sent as the complete .JSON object.

  1. If the user’s authentication in successful based on the custom logic coded by you, then the user will be able to access the application, and the details of this user can be viewed and managed in the User Management section.

  2. If the end-user’s details do not meet the authentication requirements you coded, then they will not be able to access the application.

Last Updated 2024-01-04 12:16:42 +0530 +0530