# Page Not Found

The URL `configure-integration/identity-managers/okta/okta-openid-connect` does not exist. This page may have been moved, renamed, or deleted.

## Suggested Pages

You may be looking for one of the following:
- [Okta and OpenID Connect](https://documentation.immuta.com/2024.2/people/section-contents/how-to-guides/okta-openid-connect.md)
- [Data Source Health Checks Reference Guide](https://documentation.immuta.com/2024.2/data-and-integrations/registering-metadata/data-source-settings/data-source-health-checks.md)
- [Why Use Schema Monitoring?](https://documentation.immuta.com/2024.2/data-and-integrations/registering-metadata/schema-monitoring/schema-monitoring-explained.md)
- [Reference Guides](https://documentation.immuta.com/2024.2/data-and-integrations/registering-metadata/schema-monitoring/reference-guides.md)
- [How-to Guides](https://documentation.immuta.com/2024.2/data-and-integrations/registering-metadata/schema-monitoring/how-to-guides.md)

## How to find the correct page

If the exact page cannot be found, you can still retrieve the information using the documentation query interface.

### Option 1 — Ask a question (recommended)

Perform an HTTP GET request on the documentation index with the `ask` parameter:

```
GET https://documentation.immuta.com/2024.2/people/section-contents/how-to-guides/okta-openid-connect.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

### Option 2 — Browse the documentation index

Full index: https://documentation.immuta.com/2024.2/sitemap.md

Use this to discover valid page paths or navigate the documentation structure.

### Option 3 — Retrieve the full documentation corpus

Full export: https://documentation.immuta.com/2024.2/llms-full.txt

Use this to access all content at once and perform your own parsing or retrieval. It will be more expensive.

## Tips for requesting documentation

Prefer `.md` URLs for structured content, append `.md` to URLs (e.g., `/2024.2/people/section-contents/how-to-guides/okta-openid-connect.md`).

You may also use `Accept: text/markdown` header for content negotiation.