Skip to content

Protecting a personalized portal app

A protected app is any personalized portal app that requires users to confirm their identity through a challenge app before they gain access to the personalized portal app. When users go to the personalized portal, they are first presented with a sign in page (the challenge app) and enter the required details. In the background, the personalized app initiates authentication with the endpoint that has the data. If successful, the challenge app then redirects the user to the personalized app.

To authenticate a personalized app, you configure the authentication settings of the app. This tells the portal that users can access the app only after completing the authentication process.

Prerequisites

Before you can complete the configuration of a personalized portal app as a protected app, you need to configure the challenge app.

Creating a personalized public portal app

  1. Create a new app:

    • Use case: Personalized Portal
    • Add the required providers. You can integrate with any supported data sources.
    • Add a form for the challenge app input parameters. If required, you can hide this form from the end user if its only purpose is to let you configure the authentication action. See below for details.
    • Add an action to get the data needed for authentication. This action maps to fields in the challenge app input parameters form. See below for details.
    • Configure the authentication settings. It is this step that makes the public portal app into a protected public portal app.
    • Make the app live.
    • Copy the app link from the publish link.
    • Test the protected app using your browser in incognito mode. You cannot test the app properly if you are logged in as a user in the browser.

Adding a form for the challenge app input parameters

If you are using one-time One Time Passcode (OTP) or secured links then one of the providers in the public portal app must provide the data used in the OTP challenge, such as the email address. To configure the authentication action, you add these provider properties to a form. As this form is for internal use when configuring the action, you can hide the form from the end user:

To configure a form for the challenge app input parameters:

  1. Add a form to the personalized portal app.
  2. Add the provider properties required by the challenge app to the form, such as email address, username.

You can choose to hide the form from the user because its only purpose is to let you configure the authentication action set:

  1. Add a display task to hide the form. See Display Tasks
  2. Configure an event to hide the form, for example, use the OnLoad event of the component (form) to run the display task.

Configuring a personalized portal app