UI feature configuration for 10Duke Login Application

The following feature configurations are available for 10Duke Login Application.

Registration page

  • Send an email after a user has registered to request them to verify their email address.

    Email address verification is by default required in the system. This configuration option is provided to support custom implementations where email sending from the Login Application is not in use.

    Default: Enabled

  • Which fields are displayed and in what order, and which of them are required fields.

    If the system configuration defines required fields that are not included in this configuration, those fields are still displayed after the fields defined here.

    If you want to use custom fields, contact the 10Duke Integration Support team.

The default configuration for the supported fields on the registration page:

Field Displayed Required
First name x x
Last name x x
Professional title - -
Nickname - -
Preferred username - -
Email address x x
Password x x
Password confirmation x x
Phone number - -
Freeform address - -
Street address - -
Postal code - -
Locality - -
Region - -
Country x x
User agreements x x

Regarding user agreements:

  • This configuration in practice only determines whether they’re displayed, and the system configuration determines whether an individual user agreement is required and optional.

  • If user agreement fields are enabled here but no user agreements have been defined in the system, a legacy “accept terms and conditions” checkbox is displayed as a required field.

Account activation

  • Show an input field where the user can enter the account activation code they received by email.

    This can be used as backup for cases where the code couldn’t be automatically read from the URL provided in the email (for example, due to a broken link), so that the user is able to enter the code manually on the account activation page.

    For reference, see example usage of account activation when creating a new consumer customer.

    Default: Shown

Device client activation

  • Define the list of allowed regex patterns for redirecting the end user after the activation of a device client.

    A regex pattern could allow, for example, opening an application on the end user’s device using a custom URL scheme.

    For reference, see information on handling a device client invitation for activating a device client.

Login page

  • Place the secondary login options (such as single sign-on options) in the footer of the login page instead of below the username and password input fields.

    Default: Enabled

  • Define the list of allowed domains for pages that are provided in the next parameter in the login URL, used for redirecting the user after a successful login.

    Not needed for pages that are in the same domain as the Login Application.

    Example value: https://www.externaldomain1.com, https://www.externaldomain2.com

Password reset

  • Show an input field where the user can enter the password reset code they received by email.

    This can be used as backup for cases where the code couldn’t be automatically read from the URL provided in the email (for example, due to a broken link), so that the user is able to enter the code manually on the password reset page.

    Default: Shown

  • Show the password input fields on the password reset page even if the reset password code couldn’t be read from the URL.

    Default: Shown

Profile page

  • Which fields are displayed on the personal details and contact details pages and in what order, and which of them are required fields.

    If the system configuration defines required fields that are not included in this configuration, those fields are still displayed after the fields defined here.

    If you want to use custom fields, contact the 10Duke Integration Support team.

The default configuration for the supported fields in personal details:

Field Displayed Required
First name x x
Last name x x
Professional title x -
Nickname x -
Preferred username x -

The default configuration for the supported fields in contact details:

Field Displayed Required
Phone number - -
Freeform address - -
Street address x -
Postal code x -
Locality x -
Region x -
Country x x

Logout

  • Set an automatic logout after a timeout for idle users (users who are not interacting with the UI).

    A timeout triggers a single logout (SLO). See more information on logout implementation using OIDC or SAML.

    Default: 31 minutes

  • Display a warning to an idle user informing them that they will be logged out soon.

    Default: 30 minutes

Other configurations

  • Enable the feature for managing alternative email addresses, for example, for account recovery.

    Default: Enabled

  • Enable or disable transition animations, such as flipping the page content when navigating profile pages or applying the slide-down effect for notifications.

    This configuration doesn’t affect the CSS-based animations used by the Login Application. Those can be overridden with a custom SCSS if needed.

    Default: Enabled

  • Show a floating “log in to continue” message above the login screen in cases where the user is prompted to first log in before they can access the page that they were trying to access.

    Default: Enabled

  • Show a floating message about a pending action in cases where the user must first complete authentication before they can continue the task they were trying to perform.

    Default: Enabled