Stateless registration
Stateless registration is a special type of registration which does not work based on browser registration, only on custom one. More on custom registration can be found here.
Stateless registration does not create a user profile. The Access Token created in the process has the Stateless type and is not stored in the user's device. This makes it possible to implement support for App2App authentication towards external identity schemas that do not allow you to make derived identities (like DigiD) in a custom registration script. This means the app will be registered "just in time" each time a user selects the custom registration method.
Stateless registration flow works exactly the same as the other custom registrations with the exception at the end of the registration flow:
- PIN creation handler is not triggered which means no PIN for the user session.
User Profileis not stored which results in limited SDK capabilities as part of the functions needsUser Profileas a parameter.Refresh Tokenis not stored, which means that once it's expired, it cannot refresh itself anymore and user needs to register again.
Implementation
First step in implementing the stateless registration is making sure that the configuration downloaded from the backend and added in the app, has stateless authentication enabled.
Configuration does not need to look exactly like example above. Other authentication options can be mixed with stateless authentication.> > If you do not see Stateless authentication option in your app configuration, it means that your server is placed on the Token Server (old) instead of Access (new) backend application. Please contact us in order to perform migration.
In code, in order to use stateless registration, first you need to add custom identity provider. More on custom identity providers can be found here.
Second, is calling registerStatelessUser from UserClient interface supplied with correct parameters.
