Configure pre- and post- attribute collection, and on token issuance start event custom extensions
The token issuance start event is triggered once a user completes all of their authentication challenges, and a security token is about to be issued. You can use a custom authentication extension and a custom claims provider to add this external data into tokens returned to your application.
The attributeCollectionStart is fired at the beginning of the attribute collection process and can be used to prevent the user from signing up (such as based on the domain they are authenticating from) or modify the initial attributes to be collected (such as including additional attributes to collect based on the user’s IdP).
The OnAttributeCollectionSubmit is fired after the user provides attribute information during signing up and can be used to validate the information provided by the user (such as an invitation code or partner number), modify the collected attributes (such as address validation), and either allow the user to continue in the journey or show a validation or block page.