> For the complete documentation index, see [llms.txt](https://docs.groundcover.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.groundcover.com/administer/okta-sso-onboarding.md).

# Okta SSO

To connect your Okta tenant as an identity Provider in groundcover, you must create an OIDC application

## Create Application

* Login to Okta admin portal
* Click "Applications"
* Click "Create App Integration"

  <figure><img src="https://2771001740-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FUHgqKYgCiRKdOpWQdi52%2Fuploads%2Fgit-blob-d9e2c64aec3ed09ce9e1e7a8480177f08956a2ce%2FScreenshot%202023-03-21%20at%2013.25.07.png?alt=media" alt=""><figcaption></figcaption></figure>
* In "Sign-in method" section mark "OICD - OpenID Connect"
* In "Application type" section mark "Web Application"
* Press "Next"

  <figure><img src="https://2771001740-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FUHgqKYgCiRKdOpWQdi52%2Fuploads%2Fgit-blob-616a45ac09961522f760cddca22628edc3c0ce38%2FScreenshot%202023-03-20%20at%2012.19.28.png?alt=media" alt=""><figcaption></figcaption></figure>
* Set "App Integration name" to "groundcover"
* In "Grant type" section mark only "Authorization Code"
* Set "Sign-in redirects URIs" to "<https://auth.groundcover.com/login/callback>"
* In "Assignments" section select groups
* Click "Save"

  <figure><img src="https://2771001740-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FUHgqKYgCiRKdOpWQdi52%2Fuploads%2Fgit-blob-a2ef20887622232778f6cf036829028738ab8cea%2FScreenshot%202023-03-23%20at%2014.55.38.png?alt=media" alt=""><figcaption></figcaption></figure>
* Copy application "Client ID" and "Client Secret"
* Contact your account representative and provide details above and your okta tenant url
* groundcover team will use above details to perform relevant actions on our side.
* Account representative will contact you to test e2e flow

## Create Dashboard Link (optional)

* Click on "groundcover" application
* In "General Settings" section click "Edit"
* Set "Login initiated by" to "Either Okta or App"
* In "Application visibility" mark "Display application icon to users"
* In "Login Flow" mark "Redirect to app to initiate login (OIDC Compliant)
* Set "Initiate login URI" to "<https://app.groundcover.com>"
* Click "Save"

<figure><img src="https://2771001740-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FUHgqKYgCiRKdOpWQdi52%2Fuploads%2Fgit-blob-69bdf21435073b08599aeed5e9bc6447a68e5bf6%2FScreenshot%202023-03-21%20at%2014.50.46.png?alt=media" alt=""><figcaption></figcaption></figure>

## Disable social login (recommended)

After confirming SSO works with your email address, contact your groundcover representative. Ask them to disable Google and Microsoft sign-in.

This ensures authentication occurs only through your IdP.

<div data-with-frame="true"><figure><img src="https://2771001740-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FUHgqKYgCiRKdOpWQdi52%2Fuploads%2FX9RjdG2z2vzxQtyirOmw%2Fimage.png?alt=media&amp;token=d2669b69-fafd-4ffe-bde2-5907e08ff6ba" alt="" width="179"><figcaption></figcaption></figure></div>


---

# 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://docs.groundcover.com/administer/okta-sso-onboarding.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.