Application Configuration

Introduction

Each application can have multiple configuration. An application configuration specifies the set of attributes that are associated to the application per Core Identity Type. So you could have one configuration for employees and another configuration for customers. This configuration will be used to

determinate which data a user has to enter once he will register to the application → Registration
determinate what data needs to be present in the system for all user that access the application → Attribute Elevation

Parameters

If you create a new application configuration, those are the parameters to enter.

Name	Datatype	Mandatory	Example	Description

Name	Datatype	Example	Description
Core Identity type	Drop Down	Employee	The Core Identity Type to which this configuration should apply
Target system	Drop Down	Webshop	The target system to which this configuration should apply
Identity type	Drop Down	Employee User	If there are more then one SSO enabled identity types for the selected core identity type, select which one should be affected. If you leave it empty, it will affect all.
Enabled	Checkbox	true	Whether or not the configuration is enabled or not.

Attributes

By default all mandatory attributes of the selected Core Identity Type will be added to the configuration. Those values can not be removed, as they are mandatory. But you can modify their behaviour and you are free to add any other attributes. All attributes that are added will be presented to the user upon registration. For users that already have an account, they will only be asked if any mandatory attribute is missing or if the Show elevation form on first access parameter of the client configuration is activated.

For each attribute that you will add, there are a couple of options.

Source

The source of the attribute. If it says Core Identity Type, this means it’s a mandatory attribute from the Core Identity that has not yet been changed.

Mandatory

Whether or not the attribute is required for this application. You can mark an attribute that is not mandatory on the Core Identity Type if it is mandatory for this application or client. If the value is not yet present on the current user, the attribute elevation process will be started.

Editable

Whether or not the user can edit an pre-existing value within the attribute elevation process.

Show

Whether or not a pre-existing value should be displayed on the attribute elevation process to give the user some context.

Order

The order of the attribute on the registration or attribute elevation process.