ACLs3

Add-Ons4

AI Gateway Agents4

AI Gateway Auth Strategies4

AI Gateway CA Certificates4

AI Gateway Certificates4

AI Gateway Config Stores8

AI Gateway Consumer Groups6

AI Gateway Consumers7

AI Gateway Custom Policies4

AI Gateway DataPlane Certificates3

AI Gateway MCP Servers4

AI Gateway Model Providers4

AI Gateway Models4

AI Gateway Policies4

AI Gateway SNIs4

AI Gateway Vaults4

AI Gateways4

API4

API Documentation4

API Implementation3

API Product Documentation4

API Product Version Specification4

API Product Versions4

API Products4

API Publication3

API Specification4

API Version4

API-keys3

App Auth Strategies4

Application Registrations4

Applications4

Assets4

Audit Logs7

Auth Server4

Auth Server Claims4

Auth Server Clients8

Auth Server Scopes4

Auth Settings10

Basic-auth credentials3

CA Certificates4

Catalog AI Model Implementations3

Catalog AI Model Specs3

Catalog AI Model Versions4

Catalog AI Models4

Catalog MCP Implementations3

Catalog MCP Versions4

Catalog MCPs4

Catalog Services4

Centrally Managed Consumers4

Centrally Managed Keys3

Certificates4

Cloned Plugins4

CMEK3

Config Store Secrets4

Config Stores4

Consumer Groups6

Consumers4

Control Plane Groups2

Control Planes6

Custom Domains3

Custom Plugin Schemas4

CustomPlugins4

Data-Plane Group Configurations2

DCR Providers4

DP Certificates4

Event Gateway Backend Clusters4

Event Gateway DataPlane Certificates4

Event Gateway Listener Policies8

Event Gateway Listeners4

Event Gateway Schema Registries4

Event Gateway Static Keys3

Event Gateway TLS Trust Bundles4

Event Gateway Virtual Cluster Consume Policies20

Event Gateway Virtual Cluster Policies4

Event Gateway Virtual Cluster Produce Policies16

Event Gateway Virtual Clusters4

Event Gateways4

GraphQL Cost Decorations1

HMAC-auth credentials3

Integration Instance Auth Config3

Integration Instance Auth Credentials3

Integration Instances4

JWTs3

Keys4

KeySets4

Mesh5

MTLS-auth credentials3

Networks5

Pages4

Partials4

Personal Access Tokens2

Platform IPs1

Platform Regions1

Plugins453

Portal Appearance2

Portal Audit Logs3

Portal Auth Settings9

Portal Custom Domains4

Portal Customization2

Portal Developers4

Portal Product Versions3

Portal Team Membership2

Portal Team Roles2

Portal Teams4

Portals10

Portals IP Allow List4

Private DNS3

Provider Accounts1

Realms4

Roles6

Routes8

Serverless Cloud Gateways3

Services4

Snippets4

SNIs4

System Accounts5

System Accounts - Access Tokens4

System Accounts - Roles3

System Accounts - Team Membership2

Targets3

Team Membership2

Teams5

Transit Gateways4

Upstreams4

Vaults4

patch/v3/authentication-settings#deleteReset Auth Settings

Auth Settings

Update Identity Provider

Changed on Sep 30, 2026

Updates the configuration of an existing identity provider. This operation allows modifications to be made to an existing identity provider's configuration.

patch/v3/identity-providers/{id}

Request

Base URL: https://global.api.konghq.com
URL: https://global.api.konghq.com/v3/identity-providers/{id}
Auth: one of:
- HTTP bearer
- HTTP bearer
- HTTP bearer
- HTTP bearer

Request body

enabledboolean

Indicates whether the identity provider is enabled. Only one identity provider can be active at a time, such as SAML or OIDC.

login_pathstring

The path used for initiating login requests with the identity provider.

Example request

{
  "enabled": true,
  "login_path": "myapp",
  "config": {
    "issuer_url": "https://konghq.okta.com/oauth2/default",
    "client_id": "YOUR_CLIENT_ID",
    "client_secret": "YOUR_CLIENT_SECRET",
    "claim_mappings": {
      "name": "name",
      "email": "email",
      "groups": "groups"
    }
  }
}

Response

An identity provider configuration. This response represents the configuration of a specific identity provider, which can be either OIDC or SAML.

idstring uuid

Contains a unique identifier used for this resource.

type'oidc' | 'saml'

Specifies the type of identity provider.

enabledboolean

Indicates whether the identity provider is enabled. Only one identity provider can be active at a time, such as SAML or OIDC.

login_pathstring

The path used for initiating login requests with the identity provider.

created_atstring date-time

An ISO-8601 timestamp representation of entity creation date.

updated_atstring date-time

An ISO-8601 timestamp representation of entity update date.

Example response

{
  "id": "5f9fd312-a987-4628-b4c5-bb4f4fddd5f7",
  "type": "oidc",
  "enabled": true,
  "login_path": "myapp",
  "config": {
    "issuer_url": "https://konghq.okta.com/oauth2/default",
    "client_id": "YOUR_CLIENT_ID",
    "client_secret": "YOUR_CLIENT_SECRET",
    "claim_mappings": {
      "name": "name",
      "email": "email",
      "groups": "groups"
    }
  },
  "created_at": "2022-11-04T20:10:06.927Z",
  "updated_at": "2022-11-04T20:10:06.927Z"
}

Changes

Sep 30, 2026f530bf400198 Revision changes
- warning
  added the new 400.00 enum value to the response property for the response status
- warning
  added the new 401.00 enum value to the response property for the response status
- warning
  added the new 403.00 enum value to the response property for the response status
- warning
  added the new 404.00 enum value to the response property for the response status
- warning
  added the new 409.00 enum value to the response property for the response status
Sep 25, 20264a02153f2e60 Revision changes
- breaking
  the response's body type changed from no type to object for status
- breaking
  the response's body type changed from no type to object for status
- breaking
  the response's body type changed from no type to object for status
- breaking
  the response's body type changed from no type to object for status
- breaking
  the response's body type changed from no type to object for status
- info
  removed subschema #2 from the response body allOf list for the response status
- info
  removed subschema #2 from the response body allOf list for the response status
- info
  removed subschema #2 from the response body allOf list for the response status
- info
  removed subschema #2 from the response body allOf list for the response status
- info
  removed subschema #2 from the response body allOf list for the response status
- info
  added the optional property to the response with the status
- info
  added the optional property to the response with the status
- info
  added the optional property to the response with the status
- info
  added the optional property to the response with the status
- info
  added the optional property to the response with the status
- info
  added the required property to the response with the status
- info
  added the required property to the response with the status
- info
  added the required property to the response with the status
- info
  added the required property to the response with the status
- info
  added the required property to the response with the status
- info
  added the required property to the response with the status
- info
  added the required property to the response with the status
- info
  added the required property to the response with the status
- info
  added the required property to the response with the status
- info
  added the required property to the response with the status
- info
  added the required property to the response with the status
- info
  added the required property to the response with the status
- info
  added the required property to the response with the status
- info
  added the required property to the response with the status
- info
  added the required property to the response with the status
- info
  added the required property to the response with the status
- info
  added the required property to the response with the status
- info
  added the required property to the response with the status
- info
  added the required property to the response with the status
- info
  added the required property to the response with the status
- info
  added the required property to the response with the status

Operation history (5 revisions)