Be the first to get access to new connectors. Get early access →
ConnectorBay Early access

Okta Identity Providers (BYOK) — connector documentation

  • MCP endpoint: https://byok-okta-identity-providers.connectorbay.com/mcp
  • REST API: POST https://byok-okta-identity-providers.connectorbay.com/v1/tools/{tool_name}, described by the OpenAPI 3.1 spec at https://byok-okta-identity-providers.connectorbay.com/openapi.json
  • Transport: Streamable HTTP, stateless, MCP specification 2025-06-18 or later
  • Authentication: your own Okta Identity Providers Okta API token, sent in the X-Upstream-Key header of every request (never stored, logged or cached)
  • Health: https://byok-okta-identity-providers.connectorbay.com/health · Tool schemas: https://byok-okta-identity-providers.connectorbay.com/tools.json
  • Publisher: Unify Dynamics LLC · connectorbay.com/byok-okta-identity-providers · agent@connectorbay.com

What Okta Identity Providers (BYOK) is for

Okta Identity Providers (BYOK) lets an AI assistant read your own Okta Identity Providers data through the Okta Identity Providers API with a key you supply (Okta API token). Read-only: 8 tools (list_identity_providers, get_identity_provider, list_idp_key_credentials, get_idp_key_credential, list_idp_signing_keys, get_active_idp_signing_key, list_realms, get_realm). The BYOK key travels with each request, is used for that one call only and is never stored, logged or cached; it is only ever sent to *.okta.com. Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by Okta Identity Providers. Okta Identity Providers and its logos are trademarks of their owners and are used only to say which service the connector works with.

Ask your assistant things like:

  • "Which external identity providers are configured in our Okta org?"
  • "Is Okta identity provider 0oa62b57p7c8PaGpU0h7 active, and does it provision users automatically?"
  • "When do the identity provider keys in Okta expire?"
  • "When does Okta identity provider key mXtSKC8DaBNgU8Aem6bhV3g2Eb0 expire?"
  • "Which signing keys does Okta identity provider 0oa62b57p7c8PaGpU0h7 use?"
  • "Which signing key is currently active for Okta identity provider 0oa62b57p7c8PaGpU0h7?"

What it does

  • list_identity_providers: List external identity providers (SAML, OIDC, social logins, identity verification) with type, status, protocol type and issuer mode.
  • get_identity_provider: Get one identity provider: name, type, status, protocol type, issuer mode and account-linking and provisioning actions. Credentials are not returned.
  • list_idp_key_credentials: List the org-wide identity provider key credentials (id, key type, use and dates). The key material itself is not returned.
  • get_idp_key_credential: Get one org-wide identity provider key credential by key id: key type, use, creation and expiry dates.
  • list_idp_signing_keys: List the signing keys attached to one identity provider with key id, type, use and dates. Certificates are not returned.
  • get_active_idp_signing_key: Get the active signing key of one identity provider: key id, type, use and dates.
  • list_realms: List realms (separate user populations such as partners or employees) with name, realm type, default flag and domains.
  • get_realm: Get one realm: name, realm type, default flag, email domains and dates.

BYOK key

You bring your own Okta Identity Providers Okta API token (https://developer.okta.com/docs/guides/create-an-api-token/main/). Your assistant sends it in the X-Upstream-Key header with each request. ConnectorBay uses it for that one call only: it is never stored, logged or cached, never shown in an answer, and it is only sent to *.okta.com over https, with no redirects followed. Create a key with the fewest permissions the tools need (read-only if the provider offers it), and revoke it at the provider whenever you like.

Data sources

Live from the Okta Identity Providers API (*.okta.com) with a BYOK key; documentation: https://developer.okta.com/docs/api/openapi/okta-management/management/tag/IdentityProvider/. Endpoints checked against that documentation on 2026-10-16.

What it is not

Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by Okta Identity Providers. Okta Identity Providers and its logos are trademarks of their owners and are used only to say which service the connector works with. It is read-only: it never creates, changes, sends or deletes anything in your Okta Identity Providers account.

Built for: Worldwide. Languages: English.