Security

x-ibm-oauth-provider

`x-ibm-oauth-provider` appears in the document. Its value is a string. Used by 2 providers across 17 OpenAPI documents. It sits in the `x-ibm-` namespace, so its meaning is defined by ibm tooling rather than by OpenAPI. Observed values include `fhir-server-pkce-api-provider`, `v3-internal-auth-oauth2-app-token`, `externalpingfederate`. Consistent with security — this is inferred from where the key appears and what it carries, not from any published definition.

Security x-ibm- namespace derived description
How this description was produced. It is assembled from what was measured in the corpus — where this key appears in a document, what shape its value takes, the values observed, and how many providers use it. It is not taken from a published definition, because for most extensions none exists. Read it as evidence, not as a specification. If you own this extension and want it described properly, tell us.
24 occurrences
17 documents
2 providers
vendor-named

Where it appears

Location in the documentOccurrences
other 20
securityScheme 4

What its value looks like

Value shapeOccurrences
string24

Observed values

Sampled from the specifications, most frequent first.

fhir-server-pkce-api-providerv3-internal-auth-oauth2-app-tokenexternalpingfederate

Providers publishing it

All 2.

aetnacitizens-financial-group

Why this is not in OpenAPI

Extensions exist because a provider needed something the specification would not carry. Most of what they hold is not the API contract at all — it is operational metadata about the contract: documentation, lifecycle, policy, provenance, and now agents. That metadata is usually better placed alongside the contract, in an Overlay or an APIs.json index, than crammed inside it. See everything else doing the security job.