| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
Sorry, something went wrong.
|
Preview deployment for your docs. Learn more about Mintlify Previews.
💡 Tip: Enable Workflows to automatically generate PRs for you. |
Sorry, something went wrong.
|
Preview deployment for your docs. Learn more about Mintlify Previews.
💡 Tip: Enable Workflows to automatically generate PRs for you. |
Sorry, something went wrong.
Merge the IdP and authorization-server tables into one with per-role columns, since Okta, PingFederate, and Descope document both roles. Correct statuses from vendor release notes as of 2026-08-30 (Okta XAA is now GA in Identity Engine 2026.08.1; WorkOS and Scalekit are gated early access, not shipped), swap blog and redirecting links for product docs, add Stytch, Keycloak version, Janssen, ThunderID, and Athenz, and replace the Entra row sourced from a personal blog post with a plain statement of which major IdPs have no public documentation yet. Define the status vocabulary and note draft-revision skew. :house: Remote-Dev: homespace
|
@localden do you prefer to keep this list using the current order, or make it alphabetical? I just suppose that once it grows, it will be easier to keep it alphabetically sorted from the UX point of view. |
Sorry, something went wrong.
| Back | FazBrowse Home | New Git URL |
Requested by Den Delimarsky · Slack thread
Before: The Enterprise-Managed Authorization page names example IdPs only (Okta, Azure AD, a corporate SSO system), with no statement of which vendors actually support ID-JAG today.
After: The page documents identity provider support for issuing ID-JAGs (Okta, Ping Identity, Microsoft Entra ID) and authorization servers accepting them on the MCP server side (Auth0, Keycloak, WorkOS AuthKit, Descope, Scalekit), with each row linking vendor docs or announcements, plus a pointer to the community-maintained oauth.net Cross-App Access implementations list.
Sources are vendor documentation and announcements, current as of August 2026. The new section mirrors the community-maintained disclaimer style of the client matrix and invites pull requests to keep it up to date.