Overview

The OneLogin Apps Launcher allows users to access their assigned applications directly from the launcher interface after authentication.

When configured, users can:

• View applications assigned to them

• Launch apps without re-entering credentials (if SSO is configured)

• Access apps from a centralized location

This article explains how to configure, manage, and troubleshoot the Apps Launcher.

How it works

1. Simpplr connects to your OneLogin tenant using API credentials.

2. Simpplr retrieves the list of applications available in that tenant.

3. Applications appear in the Apps Launcher.

4. End-user visibility is determined by user access configured in OneLogin.

If a user does not have access to an application in OneLogin, it will not appear in the Apps Launcher.

Who can use this feature

• App managers, Apps and links managers: Configure and manage app visibility and assignments.

• End Users: Access and launch assigned applications from launchpad in the header

Before you begin

Ensure the following:

• You have administrator permissions in OneLogin.

• Applications are already added in the OneLogin admin console.

• Users or roles are assigned to the relevant applications.

If applications are not assigned, they will not appear in the launcher.

Step 1: Create API credentials in OneLogin

1. Sign in to OneLogin as an administrator.

2. Navigate to:
   Administration → Developers → API Credentials

3. Select New Credential.

4. Enter a meaningful Name for the credential (for example, Simpplr Apps Launcher). This name will be very important if you ever need to re-access or delete the credentials.

5. Assign permissions required to access applications. For information on the permissions, refer to OneLogin documentation.

6. Select Save.

After saving, record the following: 

• Client ID

• Client Secret

Step 2: Configure OneLogin in Simpplr

1. Sign in to Simpplr.

2. Navigate to:
   Application settings → Apps & Links

3. Select OneLogin as the apps integration source.

4. Enter:

   • Client ID

   • Client Secret

   • OneLogin URL

5. Select Save.

Verification

After saving:

• Applications enabled in OneLogin appear in the Apps Launcher.

• Users see applications based on their assigned access in OneLogin.

If applications do not appear, review the Troubleshooting section.

Application visibility behavior

Changes to user access in OneLogin are reflected in the Apps Launcher after refresh.

Troubleshooting

Applications do not appear

Possible causes

• Incorrect Client ID or Client Secret

• API credential inactive

• Missing application read permissions

• Application not enabled in OneLogin

Resolution

1. Verify Client ID and Client Secret.

2. Confirm the API credential is active.

3. Validate assigned permissions.

4. Re-save the configuration in Simpplr.

Synchronization fails after credential update

If the Client Secret is rotated in OneLogin:

1. Generate the new Client Secret in OneLogin.

2. Update the Client Secret in Simpplr.

3. Select Save.

Failure to update will prevent application retrieval.

Users cannot access a specific application

Possible Causes

• User not assigned to the application in OneLogin

• Application disabled in OneLogin

Resolution

1. Verify user assignment in OneLogin.

2. Confirm the application is enabled.

3. Ask the user to refresh the Apps Launcher.

FAQs

Who manages user access?

User access is managed entirely in OneLogin.
Simpplr only retrieves and displays applications based on that access.

Does this configuration affect user login?

No. This integration does not modify authentication or SSO behavior.

How many OneLogin tenants can be configured?

One OneLogin tenant can be configured per Simpplr instance.

What happens if the API credential is deleted?

Applications will stop syncing.
You must create a new API credential and update it in Simpplr.

How often are applications refreshed?

Applications are retrieved upon configuration save and may refresh periodically.
If changes are not visible, refresh the Apps Launcher.

Best Practices

• Assign apps using roles instead of individual users for easier management.

• Periodically review role assignments.

• Test SSO configuration before assigning to large user groups.