Introduction

The CoreOne Authentication Services allows users to register for a new account. This can be done either by filling out a registration form or via auto registration in combination with an external identity provider. In both cases, the registration will result in the creation of an Core Identity. You therefore have to make sure that you have configured the appropriate application configuration, the appropriate core identity type with an role model that will lead to the provisioning of a CoreOne Suite Authentication Service user. While registering all communication attributes will be validated and optional terms and conditions / privacy policies can be checked.

Application Configuration

Whether or not the registration button is shown and what kind of data is requested off the user is determinate by the application configuration. Each authentication request is associated with a client_id. That client is linked to an application and the appropriate application configuration is used to determinate if the user can register. So you have to enable the registration enabled flag on the client and configure the application configuration to enable the registration process.

Terms and Condition / Privacy Policy

If you would like to ask the user to accept terms and conditions and / or privacy policies while registering, you have to configure them on the client.

Communication Data Validation

Each attribute of type email or mobile number will automatically validated upon registration. This means, the user has to confirm the possession by entering an OTP sent to the appropriate communication device.

Registration Origin

If you add the attributes cl_registration_origin or cl_external_origin to the core identity type, the attributes will automatically be populated with the application the user registered to and - if applicable - the external Identity Provider he came from. You can then use those attributes in things like workflows.

Registration Workflow

There is not a specific registration workflow that is beeing executed when a new user registers, but you can use the After Create workflow of the Core Identity Entity to execute any customer specific logic after an registration.