Configuration Guide
Configuration Guide
Breadcrumbs

Login Tasks

Definition

Login Task Flags are set on an Identity to indicate Self Service Tasks that they should or must perform before they can access the User Portal. Those flags are typically set by Authentication Methods but can also be managed externally (through Features and/or APIs).

By default, the following login tasks are available :

Password Related

Required

Manual Clearing

Description

PASSWORD_INIT

YES

YES

The User needs to initialize his/her Password. The old password is not required.

PASSWORD_CHANGE_REQUESTED

YES

YES

The User needs to change his/her Password. The old password may be required.

PASSWORD_CHANGE_SUGGESTED


YES

The User may change his/her Password. The old password may be required.

Security Questions Related

Required

Manual Clearing

Description

SECURITY_QUESTIONS_INIT

YES


The User needs to initialize his/her Security Questions.

SECURITY_QUESTIONS_CHANGE_REQUESTED

YES


The User needs to change or update his/her Security Questions.

SECURITY_QUESTIONS_CHANGE_SUGGESTED



The User may change or update his/her Security Questions.

MyMFA Related

Required

Manual Clearing

Description

MYMFA_MOBILE_ENROLLMENT_SUGGESTED


YES

The User needs to re-enroll a new MyMFA mobile device. Intended to force user re-enrollment upon mobile app upgrade.

These tasks have the manualClearing flag: they will be automatically be cleared when a new enrollment with the new mobile app version is confirmed.

MYMFA_MOBILE_ENROLLMENT_REQUESTED

YES

YES

Configuration

🎯

You can access the Public Access configuration :

  • by clicking on "Portal" → “Login Tasks”

  • by clicking on "System" → "Configurations" → "Business Model" and perform an import/export.

Global properties

All users must have the rights to access the feature(s) linked to the login task(s) and the portal.

Domain

Code

DataSet : Each feature starts by announcing the DataSet as following:
This is the main tag which contains all the other tags.

 
<kit:DataSet xmlns:ctd="http://www.memority.com/citadel/1_0" xmlns:ctdbpmn="http://www.memority.com/citadel/bpmn/1_0" xmlns:ctdbum="http://www.memority.com/citadel/bum/1_0" xmlns:ctdcore="http://www.memority.com/citadel/core/1_0" xmlns:ctdidm="http://www.memority.com/citadel/idm/1_0" xmlns:ctdrule="http://www.memority.com/citadel/rule/1_0" xmlns:ctdtnt="http://www.memority.com/citadel/tnt/1_0" xmlns:kit="http://www.memority.com/toolkit/1_0" xmlns:rule="http://www.memority.com/toolkit/rule/1_0" xmlns:ruleaddon="http://www.memority.com/toolkit/addons/rule/1_0" xmlns:search="http://www.memority.com/toolkit/search-expression/1_0" xmlns:security="http://www.memority.com/toolkit/security/1_0" xmlns:settings="http://www.memority.com/toolkit/addons/settings/1_0" xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
</kit:DataSet>

Login Task Configuration : Each Public Access has the following configuration to describe it.

This will be detailled in the Login Task Configuration paragraph.

Version and encoding : Each feature starts by announcing the version and encoding as following

 
<?xml version="1.0" encoding="UTF-8"?>

Login Task Properties

Properties name

Type

Mandatory

Description

Values (default value in bold)

id

String

YES

The id is the unique identifier of the Login Task
This tag contains all other tags.

-

name

String

YES

The Login Task name. It can be different from the id. It is possible to modify name property after the creation.

-

description

String

NO

Used to describe the Login Task that will be configured. It is possible to modify this property after the creation of the Login Task.

-

feature

String

YES

The Identifier of the Self-Service Feature to use for the corresponding Login Task.

-

required

Boolean

NO

Indicate whether or not the login task is required or not.

If true, once the login task is positionned on the user, he will have to complete it to be able to access the portal.

If false, he even if the login task is positionned on the user, he will be able to skip it and access the portal anyway.

false, true

manualClearing

Boolean

NO

If false, the Login Task will be considered completed as soon as the user submits the feature.

If true, the Login Task will not be cleared automatically and needs to be removed by an external mechanism, either builtin (see MYMFA_MOBILE_ENROLLMENT_REQUESTED above) or custom (e.g. API call from an external system).

false, true

Example

XML
   <ctdbum:LoginTask id="my_login_task" builtin="false">
      <name>My Login Task</name>
      <description></description>
      <feature>common-self-change-password</feature>
      <required>true</required>
   </ctdbum:LoginTask>
  • Data Model

    Describes objects and their attributes like Identity, Organization, Roles, etc.

  • Features

    Design screens and business features to manage objects.

  • Workflows

    Trigger workflows to validate an action (e.g., object, role assignment).

  • Policies

    Scheduled or triggered automatic actions on objects.

  • Public Access

    Allows unauthenticated access to certain features.

  • Notifications

    Send notifications based on object lifecycle or feature validation.

  • Synchronization

    Objects Synchronization with external accounts hosted on remote applications.

  • Reporting

    Create reports, displaying lists, aggregated data, or charts.

  • Rights

    Defines rights granted to identities via roles.

  • System

    Manages global configuration, such as files, settings, and logs.

  • Customization

    Customize colors and translations of the user portal.

  • Access

    Allow the configurator to manage access features.

  • Federation

    Integrate applications with Memority using standards like SAML, OAuth2, or OIDC