# OIDC is a standard, identity providers are not

DevFeed: [OIDC is a standard, identity providers are not](<https://devfeed.tech/articles/oidc-is-a-standard-identity-providers-are-not-16041.md>)

Original publisher: [Read original article](<https://workos.com/blog/oidc-standard-identity-providers-are-not>)

Author: WorkOS

Published: 2026-09-09T16:09:50Z

Content type: article

Language: en

Sources: [WorkOS Blog](<https://devfeed.tech/sources/workos-blog.md>)

Topics: [OpenID connect (OIDC)](<https://devfeed.tech/topics/oidc.md>), [interoperability](<https://devfeed.tech/topics/interoperability.md>), [OAuth](<https://devfeed.tech/topics/oauth.md>), [JSON Web Tokens](<https://devfeed.tech/topics/jwt.md>), [Authentication](<https://devfeed.tech/topics/authentication.md>)

Tags: [compatibility](<https://devfeed.tech/tags/compatibility.md>), [interoperability](<https://devfeed.tech/tags/interoperability.md>), [jwt](<https://devfeed.tech/tags/jwt.md>), [oauth](<https://devfeed.tech/tags/oauth.md>), [oidc](<https://devfeed.tech/tags/oidc.md>), [providers](<https://devfeed.tech/tags/providers.md>)

## AI overview

This article explains why generic OpenID Connect integrations often require provider-specific compatibility settings. It discusses differences in token-endpoint client authentication, including client secret basic, client secret POST, and private key JWT.

## Source excerpt

Generic OIDC connections meet identity providers that read the same spec differently. Here are the per-connection compatibility settings we added, and why.