> For the complete documentation index, see [llms.txt](https://docs.balkan.id/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.balkan.id/getting-started/entitlement-data-discovery/credentials-discovery/okta-credentials.md).

# Okta: Credentials

### Overview

BalkanID supports discovery and governance of credentials within Okta as part of **IGA for Non-Human Identities (NHI).**

All credentials are normalized into the BalkanID data model and surfaced in the Credentials tab, along with their associated identities, access relationships, and risk insights.

The associated credentials can also be seen under the specific application integration (Okta) page.

<figure><img src="https://2975852473-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FbVGYwk8aSk5yI1GDPEW9%2Fuploads%2FpLETIldGl4LbpLRQtSZn%2FScreenshot%202026-07-06%20at%202.21.01%E2%80%AFPM.png?alt=media&amp;token=66228b5b-9acd-4a8f-90a3-6c83f5948112" alt=""><figcaption></figcaption></figure>

### Credential Types Supported

BalkanID tracks the following Okta credential types:

{% hint style="info" %}
Note: The credential types listed below are examples and do not represent the full set of supported Okta credentials.
{% endhint %}

* App Keys
* App OAuth2 JSON Web Keys
* App OAuth2 Secrets
* App Refresh Tokens
* User API Tokens
* User Passwords
* User Refresh Tokens

### Common risks associated with Okta credentials include:

* User passwords that have never been changed since account provisioning, often indicating a default or shared credential that was never rotated.
* Users who have never authenticated with their password, or have not logged in for 90+ days, leaving stale credentials tied to orphaned or forgotten accounts.
* Org-level API tokens configured without an expiration date, remaining valid indefinitely and posing a persistent risk if leaked.
* API tokens with no IP allowlist configured, allowing usage from any network and increasing exposure if the token is compromised.
* User or application OAuth2 refresh tokens with no expiration date, extending the window for token theft and session hijacking.
* Application OAuth2 client secrets or signing keys that are inactive, never rotated since creation, or expired, increasing the risk of undetected credential compromise or authentication failures.

This ensures visibility and governance of credential-based access in 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 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.balkan.id/getting-started/entitlement-data-discovery/credentials-discovery/okta-credentials.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.