LoginSign Up
← Back to all sparks
Okta logo

Okta

INFRA · APISDEVOPS
Velocity2.5

Identity and access management platform

www.okta.com ↗

Okta adds TypeScript to its Cross App Access guides and dates the end of Classic Engine features

identitycross-app-accessai-agentsidentity-enginedeveloper-sdks
◆Current state
Okta's developer feed is still led by Cross App Access, the token-exchange grant that lets an app or agent reach a third-party API on a user's behalf from an existing SSO trust. The newest guide builds a TypeScript MCP client with it, following an earlier C# version. The other notable item is a hard date: from March 5, 2027, Okta ends support for SSR, Desktop SSO and Device Trust on Classic Engine.
◆Where it's heading
The XAA guides keep working through federation shapes and languages rather than adding a new grant. The Classic Engine notice points the same way from the platform side: customers are being moved onto Okta Identity Engine, with the end-of-support date as the push. Both threads are about adoption of what already exists.
◆Prediction
Expect more Identity Engine migration guidance ahead of March 2027, alongside further XAA walkthroughs for other languages and agent frameworks.

◆Recent moves

  1. 1mo ago

    Build a Secure TypeScript MCP Client with Cross App Access (XAA)

    The TypeScript counterpart to the earlier C# MCP guide, using an HR app and a task tracker on separate domains as the scenario. It continues the XAA series, moving from federation shapes to agent-facing languages.

    View source ↗
  2. 1mo ago

    Classic Engine Feature EOL: SSR, Desktop SSO, Device Trust

    Okta sets March 5, 2027 as the end of support for SSR, Desktop SSO and Device Trust on Classic Engine. Unlike the tutorials around it, this forces a decision on customers still running Classic Engine.

    View source ↗
  3. 2mo ago

    Supercharge Auth with Signals and the New Okta Angular SDK

    The Okta Angular SDK drops NgModule entirely — no importProvidersFrom wrapper, and guards become plain functions — bringing it in line with how standalone Angular applications are structured. It is a modernization of an existing integration path rather than new authentication capability, but it removes the boilerplate mismatch that made the SDK feel dated against current Angular projects.

    View source ↗
  4. 2mo ago

    Add Cross App Access to Your OIDC Resource Application

    The resource-application half of Cross App Access for OIDC federations: how an app that already trusts a customer's IdP for SSO reuses that same trust to authorize API access. Paired with the requesting-app guide days earlier, it completes the OIDC side of the same matrix Okta had already filled in for SAML.

    View source ↗
  5. 2mo ago

    Add Cross App Access to Your OIDC Requesting Application

    The requesting-application half of Cross App Access for OIDC, turning on the detail that it is the refresh token from sign-in, not the ID token, that gets exchanged to reach a third-party app. Continues the pattern of covering each federation topology separately so adopters never have to change protocols to use XAA.

    View source ↗
  6. 2mo ago

    I Found My Coordinates: Code, Community, and Okta

    A first-person career post from the Builder Advocacy team with no product content. It is the second narrative of its kind in this window, marking the blog's drift toward community storytelling alongside the XAA technical push.

    View source ↗