Skip to main content

Single Sign On (SSO)

The VIKTOR Platform supports Single Sign On using the OpenID Connect protocol. In this guide the configuration on Azure Active Directory is laid out. This guide will walk you through all the required steps to configure your VIKTOR application, so that it uses OpenID Connect to authenticate to your Azure Active Directory, forcing your users to access it using their Azure AD account.

Once you have completed this configuration you can enable an OpenID Connect "Log in with Azure AD" button for your VIKTOR application.

Upon request, we can customize the provider name "Azure AD" in your login button label, with the label of your choosing.

Additionally, to this guide you can see Azure - Register An App Quickstart Guide as a reference.

If Single Sign On is enabled, users will sign in using your Azure Active Directory, but there is no active synchronization between the Active Directory and the VIKTOR environment. When you remove a user from your Active Directory, this user will be blocked when trying to sign in through SSO, but the user will still be present in the users-list in the VIKTOR environment.


Users with a developer account have a second method of authentication, which is used when commands are executed from the cli (such as listing apps or publishing apps). In case you revoke access (in Azure AD) for a developer user, make sure to also manually delete the developer user in the VIKTOR environment.

Create a new Azure AD Application

First, you need to open your Azure Active Directory portal, either by logging in to your Microsoft Azure admin portal and then selecting the Azure Active Directory service, or by directly visiting To create a new application, go to App Registrations > New Registration, as shown in the screenshots below.

Here we have configured our application’s Redirect URI. If your VIKTOR application is running at https://{subdomain}, this value should be https://{subdomain}

To avoid naming inconsistencies and to make it easier for your admins and users to discover the application, you can standardize the name of your VIKTOR applications as "VIKTOR {subdomain}".

Set up the Azure AD Application

  1. Application IDs

After you have created the new application, you can find its IDs in the "Overview" page, as shown below. The Application (client) ID and Directory (tenant) ID will be used later to setup your VIKTOR application.

  1. Configure permissions

Next, you need to enable the required permissions for VIKTOR to be able to read the logged-in user’s basic information and register them to your VIKTOR application, after they have successfully logged in. Go to "API Permissions" and clear existing permissions. Add the required permissions by navigating to: Add a permission > Microsoft Graph > Delegated permissions. Select email, offline_access, openid and profile, and click "Add permissions". Click "Grant admin consent for {tenant}".

  1. Setup for Single Logout

To enable your VIKTOR application to log out a user when they log out from Azure AD, you need to specify your application’s Logout URL, in the "Authentication" page. If your VIKTOR application is running at https://{subdomain}, this value should be https://{subdomain}

  1. Create a client secret

Last, you need to create a client secret for your VIKTOR application to prove its identity when authenticating the user. Go to "Certificates & secrets" and add a client secret. Use description "Default" and expiration "Never". Copy the value of the secret for later use.

If you have other requirements concerning the expiration of this secret you are free to choose so. Please remember that when changing this secret you will have to relay the new value with us.

  1. Configure the application URL and logo

If you decide to make this application discoverable to your user via their Access Panel or the O365 app launcher, then you may want to set up your application’s home page URL, to allow redirecting to the app, and logo. To do so go to "Branding". Here we have configured our application’s Home page URL. This value should be your VIKTOR application address https://{subdomain}

Should you choose to use the VIKTOR logo, you can save and upload our official logo.

Set up the VIKTOR Application

Now that your application is ready on Azure AD, we will need the information below to setup your VIKTOR application:

  • Application (client) ID
  • Directory (tenant) ID
  • Client secret
  • (Optional) Custom provider name label to be shown in the login button, instead of "Azure AD" in "Log in with Azure AD".

You can send this information via email to your contact person.

Note: make sure to place the client secret in a file and lock it with password before sharing. Send the password separately, via SMS or phone call.

If you have different policies for sharing password or secrets, feel free to follow them. In any case, do not send the secret as plain text.

Provision the Application

At this point the VIKTOR App is registered in your Azure AD and can be used. To manage operational settings go to "Enterprise Applications" from the Active Directory main page and search for "VIKTOR". Below you can find some settings you might want to consider.

Assign application owners

To allow other users to configure and maintain the application, you can assign them as Owners. Go to Owners > Add and select the desired users.

Assign users to the application

By default, your Azure AD application will be configured to allow all your users to sign in. To allow only selected users to sign in, navigate to "Properties" and enable "User assignment required". If you want the application to be visible to the assigned users in their Access Panel and the O365 app launcher, also enable "Visible to users".

To assign users to your application, go to Users and groups > Add user and select the desired users.

For further information on how to set up user access follow this guide.

Self-service Application

An alternative to provision your application is to make your application self-service. This means that the application will be discoverable by the users that don’t have access to it, via their My Apps page, and will allow them to request access for your application. After a user has requested for access, they will still not be able to log in, until it is approved.

Self-service is not available for guest users, only for members of your organization with a P1 or P2 license.

Setup your application

To enable self-service you first need to create a group and assign it to your application. All user that will be approved to use the application via self-service will land in this group, thus acquiring access for your application. First go to "Groups" from the Active Directory main page and create a "New group". In our case, we created a group called "Test group". Then go back to the Active Directory main page, select "Enterprise applications", find your "VIKTOR" application and open "Users and groups". From this screen, assign the group you just created to your application, as shown below.

Next, go to "Self-service". From here you can:

  • enable the self-service for your application
  • select the group where the users will land once they get access
  • select whether approval will be required before the user is able to login
  • select the users responsible for approving self-service requests

To allow a member of your organization to self-service you need to assign a P1 or P2 license to them. From the Active Directory main page, go to Licenses –> All products, select your "Azure Active Directory Premium P1" or "Azure Active Directory Premium P2" license, click "Assign" and select your users.

Alternatively, you can assign the licenses via your Microsoft 365 admin center.

The self-service flow in action

After setting up self-service in your application, you have now enabled your users to request for application access via their My Apps page. By clicking on "Add self-service apps", they will see a list of application they can request access for, like shown below.

The user assigned to approve the self-service request will get an email for the application access requested by the user, like the one shown below. Approving the request will allow the user to login to the application.