> For the complete documentation index, see [llms.txt](https://docs.limio.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.limio.com/product/authentication/sso-your-authentication/use-okta-with-limio-for-customers.md).

# Use Okta with Limio for Customers

## Introduction

This guide provides step-by-step instructions for integrating Okta with Limio for authentication purposes. By completing this setup, you can enhance your system's security and streamline user authentication. This guide assumes you have admin-level access to both Okta and Limio.

Note this is for your end-users or customers, aiming to logging to manage their subscriptions. Learn more at [Set up Authentication for Customers](/product/authentication/sso-your-authentication.md).

***

## Prerequisites

Before you begin, ensure you have the following:

* Admin access to your Okta Developer Console.
* Access to the Limio platform with appropriate permissions to modify authentication settings.
* The following information prepared:
  * Your Okta domain.
  * Redirect URIs required for Limio.

***

## Okta Configuration

1. **Access Your Okta Developer Console**
   * Log in to [Okta Developer Console](https://developer.okta.com/).
2. **Create a New Application**
   * Navigate to **Applications** > **Applications** > **Create App Integration**.
   * Choose **OIDC - OpenID Connect** as the sign-in method.
   * Select **Web Application** and click **Next**.
3. **Set Up Application Settings**
   * Configure the following:
     * **Sign-in redirect URIs:**\
       `https://{tenant}-shop.prod.limio.com/api/sf`
     * **Sign-out redirect URIs:**\
       `https://{tenant}-shop.prod.limio.com/api/sf/logout`
   * Click **Save** to complete the setup.
4. **Retrieve Integration Credentials**
   * Note down the following:
     * **Client ID**
     * **Client Secret**
     * **Issuer URL** (e.g., `https://{okta-domain}/oauth2/default`)

***

## Limio Configuration

1. **Access Limio Authentication Settings**
   * Log in to Limio and navigate to **Settings > Authentication > OpenID Connect**.
2. **Add a New Authentication Provider**
   * Configure the following:
     * **Provider Name:** A unique name to identify the provider, e.g., `okta-test-dev-shop.prod.limio.com`.
     * **Issuer Name:** The Issuer URL from Okta.
     * **Client ID:** As provided by Okta.
     * **Client Secret:** As provided by Okta.
     * **JWKS URI:**\
       `https://{okta-domain}/oauth2/default/v1/keys`
     * **Authorization Endpoint:**\
       `https://{okta-domain}/oauth2/default/v1/authorize`
     * **Token Endpoint:**\
       `https://{okta-domain}/oauth2/default/v1/token`
     * **Logout Endpoint:**\
       `https://{okta-domain}/oauth2/default/v1/logout`
     * **Token Endpoint Type:** Basic
     * **Scope:** `openid profile email`
3. **Save and Test the Configuration**
   * Save the changes and test the authentication flow to ensure proper integration.

## Conclusion

You have now configured Okta as an authentication provider for Limio. For further assistance or troubleshooting, refer to the [Okta Integration Guide](https://help.okta.com/en-us/content/topics/apps/apps_app_integration_wizard_oidc.htm) or contact Limio Support.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.limio.com/product/authentication/sso-your-authentication/use-okta-with-limio-for-customers.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.