> For the complete documentation index, see [llms.txt](https://help.verkada.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.verkada.com/government-solutions/single-sign-on-sso/government-solutions-identity-providers.md).

# Government Solutions Identity Providers

Configure SSO with your identity provider for your Government Solutions organization

Integrate Verkada Command with your organization's identity provider (IdP) for Single Sign-On (SSO).

{% hint style="danger" %}
You need [Organization Admin](/command/users-and-permissions/roles-and-permissions-for-command.md) permissions to set up SSO.
{% endhint %}

***

## Supported providers

| Provider                                                                                                                                                           | SAML | SCIM |
| ------------------------------------------------------------------------------------------------------------------------------------------------------------------ | :--: | :--: |
| [Okta](broken://pages/TguzvzpVlWLAy2CJhWsB)                                                                                                                        |  Yes |  Yes |
| [Microsoft Entra ID](/government-solutions/single-sign-on-sso/government-solutions-identity-providers/microsoft-entra-id-saml-integration-government-solutions.md) |  Yes |  Yes |

***

## Generate client-ID

{% stepper %}
{% step %}
**Go to Verkada Command > All Products > Admin.**
{% endstep %}

{% step %}
**Under Login & Access, select Single Sign-On (SSO).**
{% endstep %}

{% step %}
**Click**  <i class="fa-plus">:plus:</i> **Add.**
{% endstep %}

{% step %}
Click **Copy next to your client ID.**

Save your client ID in a secure place to use in your IdP configuration.
{% endstep %}

{% step %}
**Complete your IdP configuration, then come back to complete the** [**Command configuration**](#command-configuration)**.**
{% endstep %}
{% endstepper %}

***

## Command configuration

After configuring your IdP, you'll receive an XML metadata file to upload to Command.

{% stepper %}
{% step %}
**Go to Verkada Command > All Products > Admin.**
{% endstep %}

{% step %}
**Under Login & Access, select Single Sign-On (SSO).**
{% endstep %}

{% step %}
**Click** <i class="fa-pencil-line">:pencil-line:</i> **next to your SAML configuration.**
{% endstep %}

{% step %}
**In the Identity Provider XML Metadata section, click Upload New XML.**

Upload the XML file you downloaded during your IdP configuration.
{% endstep %}

{% step %}
**In the Email Domains section, configure the email domains that users in your organization will use to log in.**&#x20;
{% endstep %}

{% step %}
**In the Verify Metadata section, click Run Login Test to verify that the setup was completed correctly. If the login tests fail, review your metadata file and associated domains.**

Common error: `app_not_configured_for_user` — This can happen when your browser has cached app access. Use an incognito browser or clear your cache and retry.

{% hint style="danger" %}
Before you can verify the XML, you must add email domains.
{% endhint %}
{% endstep %}

{% step %}
**(Optional) Toggle on Require SSO to force everyone in your organization to login with SSO.**

* Anyone using the configured email domain must go through SAML to sign in
* Provides greater control over user access
* If SAML has issues, users cannot sign in until resolved or enforcement is disabled

{% hint style="warning" %}
&#x20;You cannot require SSO until the XML has been verified.
{% endhint %}
{% endstep %}
{% endstepper %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://help.verkada.com/government-solutions/single-sign-on-sso/government-solutions-identity-providers.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.