Skip to main content
All CollectionsLearn All About Workspaces
Getting started with SSO - Microsoft Entra ID

Getting started with SSO - Microsoft Entra ID

Single sign-on allows you to login using your company credentials. Visla Single Sign-On(SSO) is based on OIDC (OpenID Connect).

Updated today

Config on your SSO provider

Navigate to Microsoft Entra ID

In Microsoft Entra ID, make sure you are in the directory where you want to set up the application. Select App registrations from the left side panel, then click New registration.

Register the Application

The application name is for your reference only — pick something that fits your organization. For supported account types, choose either single-tenant or multi-tenant, depending on your organization's setup. Select "Web" as the type for the redirect URL, and paste the Callback URLs - https://app.visla.us/sso, which you copied from Visla.

Click Register.

Add UPN Claim

Under the newly created application, go to Token configuration and add the upn optional claim to the ID token. Click the Add button and make sure the "Turn on the Microsoft Graph profile permission" checkbox is selected in the popup.

Configure Application Credentials

Create a new Client secret and copy it into Visla’s OIDC setup panel, within the Secret input. Don't turn on “Enable Single Sign-On” just yet, we still need to get the Client ID and Issuer URL for your application.

*Warning: You will need to generate a new client secret before it expires!

Client ID and Issuer URL

To complete your configuration, you need two more pieces of information. You can find both in the application's Overview section.

  • Copy the Application (client) ID into the Client ID field in Visla.

  • Under Endpoints, copy the OpenID Connect metadata document URL into the Issuer URL field.

    • Make sure you remove the “/.well-known/openid-configuration” part after pasting the URL to “Issuer URL”.

Your Visla OIDC configuration should now look similar to the example below. Turn on Enable Single Sign-On to activate SSO.

Did this answer your question?