Identity Provider Quirks: How 9 IdPs Bend SAML and OIDC
Blog post from SSOJet
Although SAML 2.0 and OpenID Connect are widely supported, identity providers differ substantially in subject identifiers, email and group claims, issuer formats, signature defaults, and SCIM behavior, creating interoperability risks for B2B applications built around one provider’s conventions. The comparison covers Okta, Microsoft Entra ID, Google Workspace, OneLogin, PingOne, JumpCloud, AD FS, Auth0, and Keycloak, highlighting issues such as Entra’s app-specific pairwise subject identifiers and GUID group claims, Google SAML applications’ minimal default attributes, Auth0’s provider-prefixed IDs, and Keycloak’s full-path group values. It recommends storing stable provider-specific identifiers rather than email addresses, configuring attribute and group mappings per customer connection, validating issuers per connection, accepting either properly signed SAML responses or assertions, and enforcing standard token checks such as audience, expiration, nonce, and signatures. To identify incompatibilities before deployment, the post presents SSOJet’s open-source mock-idp tool, which simulates the nine providers’ claim formats and edge cases locally for automated SAML and OIDC testing.
| Trend | Post Mentions | Total Month Mentions | Posts | Companies | MoM |
|---|---|---|---|---|---|
| Platform Engineering | 26 | 2,014 | 399 | 102 | +19% |
Use this post, company, and trend context to find content marketing opportunities, perform competitive analysis, or address product feature gaps via the Plushcap MCP server or the Plushcap API.