Page Comparison

...

• User verification step (optional). The external authentication methods shown in this step are configured in a protection configuration and it can be selected with registration. <index_number>.verification.protection.configuration key.
• Entering user information (obligatory). The collected information and the obligatory information are configurable. This can be set with registration. <index_number>.userinfo.fields and registration. <index_number>.userinfo.optional key.
• Multiple steps can be configured by adding fields of each step inside curly brackets. For example, registration.1.userinfo.fields = {customid, email}, {firstname, surname, mobile, acceptTerms}
• Custom attributes can be created by giving them names and adding descriptions to messages_xx.properties. For example, registration.1.userinfo.fields = firstname, surname, testikentta
• The system also supports the option to check that the user has a valid customership in the company customer information system. These are set with keys that start with registration.<index_number>.backend.
• Activation of authentication methods (optional). With this step you can, for example, force the user to print out a list of one time passwords.
  Activation step is shown if there are methods set with registration.<index_number>.methods key that are defined visible. The activated authentication methods are configurable and the desired authentication methods can be set as obligatory. Obligatory authentication methods must be activated before the user can proceed.
• Information summary (optional). This optional step shows the user entered information and asks the user to check the information before proceeding. This step requires the fields to be configured using registration.<index_number>.summary.fields. Summary step can be skipped completely with registration.<index_number>.summary.enabled = false. Even if the summary step is skipped, the summary.fields should be provided as those are also used in the confirmation view.

...