Be the first to get access to new connectors. Get early access →
ConnectorBay Early access
Discover
Okta Identity Providers (BYOK) icon

Okta Identity Providers (BYOK)

Read the external identity providers, their key credential metadata and the realms of your Okta org with your own API token. Client secrets and certificates are not returned

Unify Dynamics LLC

Tools8read-only
Sign-inBYOKbring your own key
Key keptNeverused for one call only
PriceFreeoptional Pro limits
ProviderOkta Identity Providersunofficial, not affiliated
Works withMCP · RESTany agent

Try asking

Real questions, and the tools your agent calls to answer them.

Which external identity providers are configured in our Okta org?
Tools called
list_identity_providers
Is Okta identity provider 0oa62b57p7c8PaGpU0h7 active, and does it provision users automatically?
Tools called
get_identity_provider
When do the identity provider keys in Okta expire?
Tools called
list_idp_key_credentials
When does Okta identity provider key mXtSKC8DaBNgU8Aem6bhV3g2Eb0 expire?
Tools called
get_idp_key_credential
Which signing keys does Okta identity provider 0oa62b57p7c8PaGpU0h7 use?
Tools called
list_idp_signing_keys
Which signing key is currently active for Okta identity provider 0oa62b57p7c8PaGpU0h7?
Tools called
get_active_idp_signing_key

About

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.

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.

Privacy

The publisher, Unify Dynamics LLC, states that tool inputs are processed in memory and not retained.

Data not collectedNo account, no profile, no stored prompts or results.

What it can do

8 tools, grouped by job. Every one is read-only or compute-only.

OpenAPI
Read your data8 tools
  • List identity providersList external identity providers (SAML, OIDC, social logins, identity verification) with type, status, protocol type and issuer mode.
  • Get identity providerGet one identity provider: name, type, status, protocol type, issuer mode and account-linking and provisioning actions.
  • List idp key credentialsList the org-wide identity provider key credentials (id, key type, use and dates).
  • Get idp key credentialGet one org-wide identity provider key credential by key id: key type, use, creation and expiry dates.
  • List idp signing keysList the signing keys attached to one identity provider with key id, type, use and dates.
  • Get active idp signing keyGet the active signing key of one identity provider: key id, type, use and dates.
  • List realmsList realms (separate user populations such as partners or employees) with name, realm type, default flag and domains.
  • Get realmGet one realm: name, realm type, default flag, email domains and dates.

Information

PublisherUnify Dynamics LLC
CategoryDeveloper tools
LanguagesEnglish
Built forWorldwide
CompatibilityAny MCP client · any agent · REST
Version0.1.0
MCP endpointhttps://byok-okta-identity-providers.connectorbay.com/mcp
REST APIopenapi.json
SupportGet help · Status
CountryWorldwide
FunctionOther
LayerDeep connectors

More like this

More in Other

LI.FI Earn (BYOK)

Read DeFi vault yields, TVL, protocols and wallet positions from the LI.FI Earn data API with your own API key

Live · MCP + REST5 tools

LI.FI (BYOK)

Read cross-chain bridge and swap data from LI.FI (chains, tokens, gas prices, transfer status and transfer history) with your own API key

Live · MCP + REST5 tools

Taskade (BYOK)

Read your Taskade workspaces, folders, projects, tasks, notes, members and AI agents with your own personal access token

Live · MCP + REST11 tools

Legalesign (BYOK)

Read your Legalesign e-signature documents, signing status, templates, groups and signers with your own API key

Live · MCP + REST10 tools

OpnForm (BYOK)

Read your OpnForm workspaces, forms, form submissions and workspace members with your own personal access token

Live · MCP + REST5 tools

Concord (BYOK)

Read your Concord contracts, folders, versions, summaries, members, tags, reports and activity with your own API key

Live · MCP + REST12 tools

Get Okta Identity Providers (BYOK)

Free · BYOK · Read-only

BYOK: bring your own keyThis connector uses your own Okta Identity Providers Okta API token. Create one at https://developer.okta.com/docs/guides/create-an-api-token/main/, with the fewest permissions it needs (read-only if the provider offers it). Your assistant sends it in the X-Upstream-Key header with every request. It is used for that one call only: never stored, logged or cached, and only ever sent to Okta Identity Providers. Revoke it at the provider whenever you like. Unofficial connector: not affiliated with Okta Identity Providers.