When you have more than one Pega application, you can now map a common authentication service between them, allowing users of both applications to seamlessly transition between applications without reauthenticating. You can now find the new Applications tab on the Authentication service rule form, which displays the applications to which the authentication service is mapped. The Applications tab is read-only and displays a list of the application instances for a mapped authentication services under that specific authentication service. 

If your applications have multiple authentication services mapped, and a user logs in using an authentication service that is not common to both applications, then a common authentication service cannot ensure a seamless transition between applications. The applications must share a common authentication service and the user must use that authentication service during login for the seamless transition between applications to work.

To access the Applications tab:

In the header of Dev Studio, click Records > System Admin > Authentication Service. Then, select an authentication service. Click the Applications tab.

The following figure shows the new Applications tab:

The following figure shows the “Switch application with different authentication service” message:

For more information, see:

• Mapping authentication services in Dev Studio
• Mapping authentication services in App Studio

• Switching between applications.