Skip to main content
Vantage supports single sign-on (SSO) via self-service single sign-on as well as several other supported IdPs. You can use self-service SSO to connect your SAML (Security Assertion Markup Language) Identity Provider (IdP) to your Vantage account. With self-service SSO, you can use your existing credentials to authenticate and access your Vantage account. SSO streamlines the login process since users don’t need to create a new account or remember another set of login credentials for Vantage. Vantage uses Just in Time (JIT) provisioning for user provisioning. As long as a user is granted access to your IdP, the user will be provisioned an account in Vantage when they first log in.

​
Self-Service SSO via SAML

Currently, Vantage supports self-service connection for SAML. If you’d like to connect one of the other supported IdPs (e.g., Google Workspace or Windows Active Directory), view the instructions below. If you do not see your IdP listed, contact Vantage Support.

​
What Is SAML SSO?

SAML is an XML-based open standard for exchanging authentication and authorization data between parties. It enables secure and standardized communication between identity providers, service providers, and users. SAML allows for seamless and secure access to web applications and services. Before you can connect your IdP to Vantage, you will need the following:
  • A valid account with a SAML IdP
  • Organization Owner role access to Vantage
  • Your IdP’s signing certificate and sign-on URL

​
Connect Your SAML IdP

1
From the Vantage console, navigate to the Authentication page.
2
Click New Connection.
3
Select the SAML connection type.
Create SSO integration in Vantage console
4
Copy the Single Sign-On URL and Audience URL that are provided on screen. You will need both of these URLs for your IdP’s configuration.
Configuration for SAML SSO integration in Vantage console
5
To add a logo to your connection’s thumbnail, use the provided Vantage Logo.
6
Once you create the Vantage application within your IdP, copy the following information:
  • Copy the SAML Sign-On URL provided by your IdP, then paste it into the SAML 2.0 Endpoint field of the Vantage SAML page.
  • Copy the Signing Certificate provided by your IdP, then paste it into the Public Certificate field of the Vantage SAML page.
7
Ensure you’ve entered the correct credentials, then click Create Connection. You’ll be redirected back to the Authentication page, where you will be able to see your connection.
8
To enable the connection, switch the Active toggle to on. You will remain logged in to Vantage, but the next time you attempt to log in, you will be redirected to your IdP’s sign-on page.
9
Optional: If you would like to set up SSO group mappings based on your existing Vantage teams, see the SSO Group Mappings instructions below.

​
View Connection Details

Once your identity provider is connected, you can view connection details on the Authentication page.

​
Associated Domains

The connection details include a Domains section that displays all domains associated with your identity provider. This section shows the email domains that are configured to use this SSO connection for authentication. When users with email addresses from these domains attempt to log in to Vantage, they will be redirected to your configured identity provider.

​
Example: Create a SAML SSO Connection with Okta

For detailed instructions, see the Okta support documentation.
1
Create an app integration on Okta.
2
For Sign-in method, select SAML 2.0. Click Next.
Create a new Okta app integration
3
For App Name, enter Vantage.
4
For App Logo, upload the Vantage Logo, then click Next.
Okta app settings
5
Enter the requested Single sign on URL (for example, https://auth.vantage.sh/login/callback?connection=company-com) and Audience URI (SP Entity ID) (for example, urn:auth0:vantage-production:company-com), provided on the Vantage Authentication setup page.
Okta SAML settings
6
Set the Application username to Email.
7
Once the app integration is set up, copy the Okta-provided Identity Provider Single Sign On URL and X.509 Certificate back into Vantage.
8
To enable the connection, switch the Active toggle to on. You will remain logged in to Vantage, but the next time you attempt to log in, you will be redirected to the Okta sign-on page.

​
Test Your SSO Configuration

The recommended steps for testing your SSO configuration are as follows:
1
Once your connection is enabled, do not close or log out of your current Vantage application session.
2
Open a private browser or incognito window, and visit https://console.vantage.sh.
3
Enter your email address. If your SSO connection is configured correctly, you will be redirected to your IdP.
4
Enter your login credentials. If you can complete the login, your configuration is correct.
If you experience any issues with logging in after you’ve enabled your connection, contact Vantage Support.

​
Rotate Your SAML Signing Certificate

SAML signing certificates issued by your IdP have an expiration date. When a certificate is approaching expiration, you need to update the certificate in Vantage before it expires to avoid SSO login disruptions.
1
In your IdP, generate or obtain the new X.509 signing certificate. The certificate can be in PEM (.pem) or CER (.cer) format.
2
Send the updated certificate to Vantage Support using a secure file transfer method.
3
Vantage will update the signing certificate on your connection. Once Vantage confirms the update, test the connection in a private or incognito browser window before ending your current session. See Test Your SSO Configuration for the recommended testing steps.
SAML signing certificates are currently updated by Vantage Support rather than directly in the Vantage console. Plan your rotation before the certificate expires so there is time to update the connection and test it.
Set a calendar reminder before your IdP signing certificate’s expiration date to avoid SSO login disruptions.

​
Disconnect Your IdP

If you ever need to disconnect your IdP from Vantage:
1
Navigate to the Authentication page.
2
To disable your connection, switch the Active toggle off. To permanently remove your IdP, click the Delete button.
After disabling/removing the connection, you will be able to log in to the app with your original Vantage login credentials.

​
Set Up Other IdPs

If you do not see your IdP listed, please contact Vantage Support.

​
Authenticate with Azure AD

The following instructions are based on the Microsoft documentation.

​
Step 1 - Obtain Your Primary Domain from Microsoft Entra ID

Obtaining primary domain from Entra ID

Source: Microsoft

1
Log in to the Azure portal.
2
Navigate to Microsoft Entra ID.
3
On the Overview screen, copy the Primary domain to use in the last step.

​
Step 2 - Register an OAuth Application with Azure

Configuration for Azure app registration

Source: Microsoft

1
From the Azure portal, navigate to App registrations, then click New registration.
2
Enter a name for your app (e.g., Vantage).
3
Set the Supported account types option to the appropriate setting for your organization.
4
For Redirect URI, select Web and enter https://auth.vantage.sh/login/callback.
5
Click Register.
6
Once the app registration is complete, copy the Application (client) ID displayed on the app’s Overview page to send to Vantage.

​
Step 3 - Generate a Client Secret

Configuration for Azure client secret

Source: Microsoft

1
On the left navigation, select Certificates & secrets.
2
Under the Client secrets tab, click New client secret.
3
Enter a description and select an expiration for the secret.
Azure client secrets have a set expiration date. If your secret expires, your SSO connection will stop working. Generate a new secret in Azure before the expiration date and contact Vantage Support with the new secret value so the connection can be updated. See Update Your Client Secret below.
4
Click Add.
5
Copy the secret’s Value.

​
Step 4 - Add API Permissions

Configuration for Azure app API permissions

Source: Microsoft

1
On the left navigation, select API permissions.
2
Select Add a permission.
3
Under the Microsoft APIs tab, find and select the appropriate permissions required by Vantage (e.g., Directory.Read.All, User.Read).
4
At the bottom, click Add permissions.
Configuration for Azure app admin consent

Source: Microsoft

1
Still under API permissions, you may see a section for Grant admin consent for {your domain}.
2
Click Grant admin consent, and follow the prompts.

​
Step 6 - Add Credentials to Vantage

1
Navigate to the Authentication screen in Vantage.
2
Select AzureAD.
3
Under Step 2, enter the following information:
  • Primary Domain: The value you obtained in step 1. Ensure you enter only the domain name (e.g., yourcompany.com). Do not include http://www.
  • Client ID: The client ID you obtained in step 2.
  • Client Secret: The secret you obtained in step 3.
4
Click Configure Connection.
After your connection is complete, if you would like to set up SSO group mappings based on your existing Vantage teams, see the SSO Group Mappings instructions below.

​
Update Your Azure AD Client Secret

The client secret you created in Step 3 has an expiration date set in Azure. Unlike the Azure cost integration, SSO connection credentials are not editable through the Vantage console. To rotate your client secret:
1
In the Azure portal, navigate to your Vantage app registration, then go to Certificates & secrets.
2
Under the Client secrets tab, click New client secret to generate a new secret. Copy the secret Value.
3
Contact Vantage Support with your new client secret value. Vantage will update the connection on their end.
4
Once Vantage confirms the update, you can delete the old secret from your Azure app registration.
Azure AD client secrets are currently updated through Vantage Support rather than directly in the Vantage console. Generate the replacement secret before the existing one expires so you can update the connection without interrupting sign-in.
Set a calendar reminder before your client secret’s expiration date to avoid SSO login disruptions.

​
Azure Government Cloud (GCC High)

The Azure AD OAuth connection uses the standard Microsoft identity endpoint (login.microsoftonline.com) and does not support Azure Government Cloud (GCC High) tenants. If your organization uses a GCC High tenant (login.microsoftonline.us), use SAML-based SSO instead. Configure your GCC High Microsoft Entra ID tenant as a SAML Identity Provider by creating an Enterprise Application for Vantage in your GCC High tenant.

​
Authenticate with Google Workspace

The following instructions are based on the Google documentation.

​
Step 1 - Register an OAuth Application with Google

1
From the Google API Console, select an existing project or click CREATE PROJECT.
2
From the left navigation menu, click Credentials.
3
At the top, click CREATE CREDENTIALS > OAuth client ID.
If this is your first time working with this Google project, you will have to configure your consent screen. Follow the Google documentation linked above.
4
For Application type, select Web application.
5
Enter a Name for your application (e.g., Vantage).
6
For Authorized JavaScript origins, click ADD URI and enter https://auth.vantage.sh.
7
For Authorized redirect URIs, click ADD URI and enter https://auth.vantage.sh/login/callback.
8
Click CREATE.

​
Step 2 - Obtain Application Credentials and Contact Vantage Support

  • Copy your app’s CLIENT ID and CLIENT SECRET.
  • Contact Vantage Support for information on how to send these credentials to finish connecting with the Vantage app.
After your connection is complete, if you would like to set up SSO group mappings based on your existing Vantage teams, see the SSO Group Mappings instructions below.

​
Authenticate with Rippling

Vantage is available in the Rippling App Shop, where you can find instructions for connecting your Vantage account to Rippling.

​
Set Up SSO Group Mapping for Teams

With the SSO Team Assignment feature, you can automatically assign users to Vantage teams that match the name of a corresponding SSO group.

​
Prerequisites

To use the SSO Team Assignment feature, you will need to have teams already set up in Vantage. See the Role-Based Access Control: Create Teams documentation for information on how to create teams in Vantage.

​
Enable SSO Team Assignment

1
From the top menu of the Vantage console, click Settings.
2
On the left navigation menu, select Authentication. You will see your SSO connection listed.
3
In the SSO Team Assignment section of the connection, click the toggle button to enable the feature.
Vantage will match SSO groups to Vantage teams based on the case-sensitive name of the SSO group. If a team name in Vantage matches an SSO group name, the user will be placed into that team in Vantage. Users will be mapped into the appropriate teams during their next login.
After the SSO Team Assignment setting is enabled, users will be removed from Vantage teams that are not present in the SSO groups. If you want to modify this behavior, contact support@vantage.sh. The Everyone team will remain unchanged.

​
Create Custom Mappings

If your team names in Vantage do not match your identity provider, or you want multiple groups to be added to the same team, you can create custom mappings.
1
To create custom mappings, click the Show dropdown menu next to Custom Mappings.
2
In the SSO Group Name column, enter the group names from your SSO provider. The SSO Group Name you enter should match the corresponding name in your identity provider. Note that the mapping is case-sensitive.
3
From the Vantage Team dropdown, select the corresponding Vantage team.
4
Click Add to add additional mappings.
SSO team assignment toggle in the console
5
When you are finished, click Save.
A user’s teams are updated on every login. Vantage will also automatically remove users from teams that are no longer present in the SSO groups list.

​
Group Mapping in Okta - Enabling groups Attribute

Vantage uses the groups field in the SSO payload for matching SSO groups to Vantage teams. As long as your identity provider can pass a groups attribute in the payload, you can use SSO group mapping. For some providers, like Okta, you may need to enable group mapping. To enable group mapping in Okta:
1
Navigate to the Vantage SAML application in Okta.
2
Edit your SAML Settings.
3
For Name, enter groups.
4
If you would like to pass through all groups, set the Filter to Matches regex with a value of .*.
Okta group attribute settings
If you need help with your specific identity provider, contact support@vantage.sh.

​
Troubleshooting

​
SSO Group Mapping Not Working

If users are not being placed into the expected Vantage teams after logging in:

​
Login Redirects to Wrong Page or Fails

If users encounter errors when attempting to log in via SSO:
  • Verify the Single Sign-On URL and Audience URL in your IdP match the values shown on the Vantage Authentication page.
  • For Azure AD, ensure the Redirect URI is set to https://auth.vantage.sh/login/callback.
  • For Azure AD, ensure the Client Secret in Vantage is the secret Value, not the secret ID.
  • If Azure AD returns a public client flow error, such as Proof Key for Code Exchange is required for cross-origin authorization code redemption, confirm the redirect URI is configured under Web, not Single-page application or Mobile and desktop applications. In Authentication > Advanced settings, ensure Allow public client flows is set to No.
  • Check that the signing certificate has not expired. If it has, follow the steps in Rotate Your SAML Signing Certificate to update the certificate.
  • If the connection was recently set up, test in a private/incognito window before logging out of your existing session. See Test Your SSO Configuration for the recommended testing steps.