Application Portal configuration in the Loginapp UI

The application portal is a web UI in the loginapp that displays accessible applications and services to the end-user. It may be used as starting point after login and is implemented as a protected self-service.

The application portal is implemented as a protected self-service feature of the Loginapp UI. There is no public REST API for the portal.

The portal displays the following elements:

The Application Portal Targets are not directly linked to the target applications in the authentication flow – only target applications explicitly configured in the application portal are shown.

0. To enable the portal and to add applications, proceed as follows:
1. Go to:
   Loginapp >> UI Settings >> Protected Self-Service UIs
2. In property Application Portal, create and edit an Application Portal UI plugin. This will enable the portal.
3. In property Portal Groups, create and edit an Application Portal Group. Note that the order of the groups in the list directly influences how they are displayed.
4. In property Identifier, set a unique identifier for the group. Remember it for later customization.
5. In property Portal Targets, create and edit one or more Application Portal Target plugins.
6. Configure each Application Portal Target as required. In property Redirect Target, set the URL or service to be called when the corresponding application logo in the portal is clicked.

To display the portal after successful authentication, the UI configuration of the corresponding authentication flow(s) needs to be adapted.

1. Go to:
   Loginapp >> UI Settings >> Authentication UIs >> Flow UIs >> <corresponding application>
2. In property Target URI Resolver, create and edit a Target URI Resolver plugin.
3. In property Default Value, set the URL to the portal page (e.g. /auth/ui/app/protected/portal)
4. This configuration ensures, that the portal is shown after successful authentication with the corresponding authentication flows.

The portal is typically shown to the user, if no specific target application is accessed or if the URL the user attempted to access is not allowed.

To achieve this, simply apply the above configuration steps for the default application. The default application's ID is defined in Loginapp >> Applications and Authentication.

To provide the text elements for portal groups and target applications, use the Loginapp Design Kit.

The identifiers chosen in the configuration are used as in the following example (src/assets/custom/i18n/en.properties):

copy

# title for group with identifier "banking-apps-group"
protected.application-portal.group.banking-apps-group.title = Banking applications


# description for group with identifier "banking-apps-group"
   protected.application-portal.group.banking-apps-group.description = Here goes your text.

# label of application with identifier "ebanking"  
protected.application-portal.group.banking-apps-group.target.ebanking.title = E-banking

To change the application logos shown in the application portal, use the Loginapp Design Kit.

The logos displayed in the portal are implemented as background images on the corresponding HTML elements. The background image can be set by applying custom styles to change the logo for a target application.

The application identifier chosen in the configuration is used as in the following example (src/sass/custom/_custom-styles.scss):

copy

// logo for application portal with id "ebanking"
#iamApplicationPortalTarget-ebanking > .iam-application-portal-target-link > .iam-application-portal-target {
	background-image: url(custom-asset('img/bank-logo.svg'));
}

• Application portal
• Customizing Loginapp UI texts and changing translations with the Loginapp Design Kit
• Change the Loginapp UI appearance with the Design Kit