> For the complete documentation index, see [llms.txt](https://docs.uibakery.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.uibakery.io/on-premise/sso/openid/okta-odic.md).

# Okta ODIC

Follow these steps to integrate UI Bakery with Okta OIDC

## Create Okta App Integration

Log in to your Okta admin dashboard and create a new app integration.

* Choose **OIDC** Sign-in method;
* Select **Web Application** as application type\\

  <figure><img src="https://837703843-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FUX6zPRMFFK0yrTghj7cY%2Fuploads%2Fgit-blob-7e6253aa5fc90aed293ee238a0d0140d9ded4161%2Fimage%20(140).png?alt=media" alt="" width="375"><figcaption></figcaption></figure>
* Enter integration name;
* Set the grant type to **Authorization code;**
* Enter sign-in redirect URI as `https://YOUR_INSTANCE/auth/oauth2/callback`

<figure><img src="https://837703843-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FUX6zPRMFFK0yrTghj7cY%2Fuploads%2Fgit-blob-ad6240577ddebea5a1423c9b5a06716a94bd41f4%2Fimage%20(137).png?alt=media" alt="" width="375"><figcaption></figcaption></figure>

***

## Configure UI Bakery environment variables

Set the following environment variables in your UI Bakery instance. You can find the clientId and clientSecret in the Okta integration's General tab. Replace `MYORG` in URLs with your Okta company name.

```
UI_BAKERY_OAUTH_CLIENT_ID=yourclient
UI_BAKERY_OAUTH_SECRET=yousecret
UI_BAKERY_OAUTH_SCOPE=openid email offline_access profile
UI_BAKERY_OAUTH_AUTH_URL=https://MYORG.okta.com/oauth2/v1/authorize
UI_BAKERY_OAUTH_TOKEN_URL=https://MYORG.okta.com/oauth2/v1/token
UI_BAKERY_OAUTH_USERINFO_URL=https://MYORG.okta.com/oauth2/v1/userinfo
UI_BAKERY_BRANDING_AUTH_SSO_BTN_TEXT=Login with Okta
```


---

# 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.uibakery.io/on-premise/sso/openid/okta-odic.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.