---
title: "Okta"
slug: "okta-1"
updated: 2025-11-18T09:13:51Z
published: 2025-11-18T09:13:51Z
canonical: "docs.connect.visma.com/okta-1"
---

> ## Documentation Index
> Fetch the complete documentation index at: https://docs.connect.visma.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Okta

## Step by step guide to configure Okta as a SAML Identity Provider within Visma

Follow the steps below to configure **Okta** as a SAML Identity Provider within Visma. Keep Authentication Settings open in your browser while you access Okta in a new window or tab. You will need to return to the Single Sign-On page to complete the configuration steps.

### Prerequisites

- Okta account
- All of your users under your account in Visma will need a pre-existing account in Okta with exactly the same email address.

### Configure Visma Single Sign-On app in Okta

1. On the Single Sign-On page go to section **1. Configure Visma metadata details into Okta**

![AuthSettings_SSO_Okta_Step1](https://cdn.document360.io/0ec30182-e256-4eca-ab6a-d067d83d0895/Images/Documentation/AuthSettings_SSO_Okta_Step1.png)
2. Log into your **Okta administrative portal.**
3. Go to left menu and click **Applications**. Select **Applications**.
4. Click **Create App Integration**.

![AuthSettings_SSO_Okta_Step4](https://cdn.document360.io/0ec30182-e256-4eca-ab6a-d067d83d0895/Images/Documentation/AuthSettings_SSO_Okta_Step4.png)
5. Select **SAML 2.0** and click **Next**.

![AuthSettings_SSO_Okta_Step5](https://cdn.document360.io/0ec30182-e256-4eca-ab6a-d067d83d0895/Images/Documentation/AuthSettings_SSO_Okta_Step5.png)
6. Name your application and click **Next**.

![AuthSettings_SSO_Okta_Step6](https://cdn.document360.io/0ec30182-e256-4eca-ab6a-d067d83d0895/Images/Documentation/AuthSettings_SSO_Okta_Step6.png)
7. Copy the **SAML Assertion Consumer** link from Authentication Settings and paste this link into the **Single sign on URL**.
8. While on the “Create SAML Integration” page copy the **Entity ID** from Authentication Settings and paste it into the **Audience URI** (SP Entity ID) field in Okta.
9. For **Name ID Format** select **EmailAddress**.
10. For **Application username** select **Email**.
11. For **Update application username** select **Create and update.**

![AuthSettings_SSO_Okta_Step11](https://cdn.document360.io/0ec30182-e256-4eca-ab6a-d067d83d0895/Images/Documentation/AuthSettings_SSO_Okta_Step11.png)
12. Click on **Show Advanced Settings**.
13. Enable **Allow application to initiate Single Logout.**
14. While on the “Create SAML Integration” page copy the **SAML Logout** from Authentication Settings and paste it into the **Single Logout URL** field in Okta.
15. While on the “Create SAML Integration” page copy the **Entity ID** from Authentication Settings and paste it into the **SP Issuer** field in Okta.
16. **You only need to do this step if you want to enable the Single Logout feature**. Return to the Authentication Settings and download the **Public certificate**, While on the “Create SAML Integration” page click **Browse** and upload the downloaded certificate and then click **Upload Certificate**.

![AuthSettings_SSO_Okta_Step16](https://cdn.document360.io/0ec30182-e256-4eca-ab6a-d067d83d0895/Images/Documentation/AuthSettings_SSO_Okta_Step16.png)
17. While on the “Create SAML Integration” page for section **Attribute Statements (optional)** copy the 2 attributes from Authentication settings section **2. Configure claims in Okta**.

![AuthSettings_SSO_Okta_Step17](https://cdn.document360.io/0ec30182-e256-4eca-ab6a-d067d83d0895/Images/Documentation/AuthSettings_SSO_Okta_Step17.png)
18. Leave all other fields empty and click **Next**.
19. Select the applicable option and click **Finish**.

### Configure Visma Single Sign-On to use Okta.

1. While on your newly created application in Okta, right click the **Identity Provider metadata link** and copy the link address. Your Metadata XML link address should look like: https://xxxxxxxx.okta.com/app/xxxxxxxx/sso/saml/metadata

![AuthSettings_SSO_Okta_ConfigureVisma_Step1](https://cdn.document360.io/0ec30182-e256-4eca-ab6a-d067d83d0895/Images/Documentation/AuthSettings_SSO_Okta_ConfigureVisma_Step1.png)
2. Paste this Metadata XML link address into the Single Sign-On page within Authentication Settings. It contains all your Okta endpoints and public certificate that Visma needs in order to complete the setup.
3. Click **Preview Data**.

![AuthSettings_SSO_Okta_ConfigureVisma_Step3](https://cdn.document360.io/0ec30182-e256-4eca-ab6a-d067d83d0895/Images/Documentation/AuthSettings_SSO_Okta_ConfigureVisma_Step3.png)
4. Continue with your Advanced configuration and click **Save**.

![AuthSettings_SSO_Okta_ConfigureVisma_Step4](https://cdn.document360.io/0ec30182-e256-4eca-ab6a-d067d83d0895/Images/Documentation/AuthSettings_SSO_Okta_ConfigureVisma_Step4.png)

### Testing Single Sign-On after Visma has made its configuration

To make sure SSO is working, perform these steps

1. To test SSO access go to your Visma MyDomain e.g. https://example.my.connect.visma.com directly, and then click the Sign in with Okta button.

![AuthSettings_SSO_Okta_Test_Step1](https://cdn.document360.io/0ec30182-e256-4eca-ab6a-d067d83d0895/Images/Documentation/AuthSettings_SSO_Okta_Test_Step1.png)

## Configure claim to expose 2-step verification claim with Visma

By default, Okta does not share a user's Multi-Factor Authentication (MFA) status with applications. However, you can configure a custom claim to pass this information to Visma during authentication.

To do this, follow the Okta guide on adding the `session.amr` value as a claim to your Visma application configuration: [https://help.okta.com/en-us/content/topics/apps/pass-authn-context.htm](https://help.okta.com/en-us/content/topics/apps/pass-authn-context.htm)
