Buildkite vs Okta

Okta's developer channel is running two threads at once. The dominant one is Cross App Access — the Identity Assertion Authorization Grant that lets an application or agent reach a third-party API on behalf of a user by exchanging tokens from an existing SSO trust. Since XAA was introduced in April, the output has been a systematic matrix of adoption guides: SAML requesting apps, SAML resource apps, and now the OIDC requesting and resource sides, plus listing XAA connections on the Okta Integration Network. The second thread is SDK and tutorial work, of which the Angular SDK going fully standalone is the substantive item.

This is a feed of developer-education posts rather than release notes, so it reads cadence rather than shipping — but the shape of the education is itself the signal. Okta is not adding new XAA capability; it is removing every remaining excuse not to adopt it, one federation topology at a time, so that neither a SAML shop nor an OIDC shop has to migrate first. The Angular SDK release points the same direction from the client side, dropping NgModule for standalone providers and function guards so the SDK matches how current Angular applications are actually written.

With OIDC and SAML now covered on both the requesting and resource sides, the remaining gaps in the matrix are framework SDKs and the agent runtimes themselves — expect XAA walkthroughs for more languages and agent frameworks in the vein of the earlier C# MCP post, rather than a new grant type.