--- title: "How to add the SAML provider to Segura®" slug: "administration-how-to-add-the-saml-provider-to-senhasegura" updated: 2026-03-04T12:03:10Z published: 2026-03-04T14:36:29Z canonical: "docs.senhasegura.io/administration-how-to-add-the-saml-provider-to-senhasegura" --- > ## Documentation Index > Fetch the complete documentation index at: https://docs.senhasegura.io/llms.txt > Use this file to discover all available pages before exploring further. # How to add the SAML provider to Segura® To finish setting up SSO for remote users in Segura® SAML provider . In this article, you'll find a step-by-step guide for this task. Info Segura® partnered with Okta to develop this documentation. The steps may vary and require adaptation for use with other providers. ## Step 1: Collect information 1. In your Okta account, go to the administration area. Info If you don't automatically enter the administration area, click the Admin button in the top right corner of the screen. 1. In the top left corner menu, select **Applications > Applications**. 2. Find the Segura® SAML application that you integrated. 3. Click on the application. 4. In the **Sign On** tab, locate the **Metadata details** field. 1. Copy the displayed URL to use in the next step. 5. Still on the **Sign On** tab, click **More details**. 6. Locate the **Sign on URL** field. 1. Copy the displayed URL to use in the next step. ## Step 2: Choose the environment to register the SAML provider Segura® allows two types of environments for SAML provider registration: - **SAML Provider in the Domum Remote Access environment**: SSO access for internal users and third-party users via Domum. - **SAML Provider in the Local environment**: SSO access only for internal users via the local network. This option suits internal users already connected to the company's internal network. Caution It’s possible to register both environments to internal users. However, it requires creating a separate application for each environment in the Okta provider. The system won’t allow registering the same application for both the **Local** and **Domum Remote Access** environments. ### Option 1: Add the SAML provider for access Info This provisioning is exclusively for internal users. 1. On Segura®, in the navigation bar, hover over the **Products menu** and select **Settings**. 2. In the side menu, select **Authentication > SAML > Providers**. 3. Click the **Add** button. 4. In the registration screen: Caution Don’t insert the right slash at the end of the URL. 1. In the **Type*** field, select **Okta**. 2. In **Enable***, check **Yes**. 3. In **Environment***, check **Local**. 4. In **Entity ID***, enter the name registered in the **General Settings** when [creating the application](/v4-2/docs/administration-how-to-create-a-saml-application-with-okta). Example: `MyAppExample`. 5. In **SAML provider metadata URL***, paste the value Okta automatically generated in the **Metadata details** field. Example: `https://trial-3650301.okta.com/app/exk6r8qx6pDaZv6IP697/sso/saml/metadata`. 6. In **Domain or public IP for URL Redirection***, enter the Segura® default URL. Example: `https://mysenhasegura.com`. 1. The system will automatically complete the **Redirect URL*** field. 2. In **SSO Login URL (Sign-in URL)*** , paste the value Okta automatically generated in the **Sign on URL** field. Example: `https://trial-3650301.okta.com/app/trial-3650301_testesso1_1/exk6r8qx6pDaZv6IP697/sso/saml`. 3. In **SSO Logout URL (Sign-out URL)**, enter the URL of the Okta application. Example: `https://trial-3650301.okta.com/`. 4. In **Redirect binding type**, select **REDIRECT**. 5. In the **Security SAML** section: Info If you haven't saved the certificate information, In this example, it can be found in the Okta administration area. 1. Download the provider's certificate and copy its content. 2. In **Certificate (PEM format)**: paste the certificate content. 6. Click **Save**. ### Option 2: Add the SAML provider for access via Domum Info This provisioning works for both Domum internal and third parties users. 1. On Segura®, in the navigation bar, hover over the **Products menu** and select **Settings**. 2. In the side menu, select **Authentication > SAML > Providers**. 3. Click the **Add** button. 4. In the registration screen: Caution Don’t insert the right slash at the end of the URL. 1. In the **Type*** field, select **Okta**. 2. In **Enable***, check **Yes**. 3. In **Environment***, check **Domum Remote Access**. 4. In **Entity ID***, enter the name registered in the **General Settings** [when creating the application](/v4-2/docs/administration-how-to-create-a-saml-application-with-okta). Example: `MyAppExample.` 5. In **SAML provider metadata URL***, paste the value Okta automatically generated in the **Metadata details** field. Example: `https://trial-3650301.okta.com/app/exk6r8qx6pDaZv6IP697/sso/saml/metadata`. 6. In **Domain or public IP for URL Redirection***, enter the Segura® default URL. Example: `https://mysenhasegura.com`. 1. The system will automatically complete the **Redirect URL*** field. 2. In **SSO Login URL (Sign-in URL)*** , paste the value Okta automatically generated in the **Sign on URL** field. Example: `https://trial-3650301.okta.com/app/trial-3650301_testesso1_1/exk6r8qx6pDaZv6IP697/sso/saml`. 3. In **SSO Logout URL (Sign-out URL)**, enter the URL of the Okta application. Example: `https://trial-3650301.okta.com/`. 4. In **Redirect binding type**, select **REDIRECT**. 5. Click **Save**. Now, Segura® can offer SSO login for internal users, and the access provider will take care of the authentication.