# Okta Developer

Secure, scalable, and highly available authentication and user management for any app.

This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles.

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

DevFeed: [Build a Secure TypeScript MCP Client with Cross App Access (XAA)](<https://devfeed.tech/articles/build-a-secure-typescript-mcp-client-with-cross-app-access-xaa-84283.md>)

Original publisher: [Read original article](<https://developer.okta.com/blog/2026/10/09/typescript-mcp-sdk-cross-app-access>)

Author: Akanksha Bhasin

Published: 2026-10-09T05:00:00Z

Content type: tutorial

Language: en

Sources: [Okta Developer](<https://devfeed.tech/sources/okta-developer.md>)

Topics: [cross-app-access](<https://devfeed.tech/topics/cross-app-access.md>), [MSP MCP](<https://devfeed.tech/topics/msp-mcp.md>), [OpenID connect (OIDC)](<https://devfeed.tech/topics/oidc.md>), [Test-driven development](<https://devfeed.tech/topics/tdd.md>)

Tags: [cross-app-access](<https://devfeed.tech/tags/cross-app-access.md>), [jwt](<https://devfeed.tech/tags/jwt.md>), [mcp](<https://devfeed.tech/tags/mcp.md>), [mcp-server](<https://devfeed.tech/tags/mcp-server.md>), [node](<https://devfeed.tech/tags/node.md>), [node-js](<https://devfeed.tech/tags/node-js.md>), [npm](<https://devfeed.tech/tags/npm.md>), [oauth](<https://devfeed.tech/tags/oauth.md>), [oauth-2-0](<https://devfeed.tech/tags/oauth-2-0.md>), [oidc](<https://devfeed.tech/tags/oidc.md>), [typescript](<https://devfeed.tech/tags/typescript.md>), [xaa](<https://devfeed.tech/tags/xaa.md>)

### AI overview

A TypeScript tutorial builds an MCP requesting app that uses Cross App Access to obtain delegated access to a protected resource. It walks through the OAuth and token exchange steps, explains ID-JAG claims, and configures the MCP TypeScript SDK's CrossAppAccessProvider, including authentication and scope adjustments for the xaa.dev playground.

### Source excerpt

Enterprise apps rarely work alone. Imagine this scenario: HR wants to ensure that a new employee completes their new hire onboarding, and they want this verification in the company's HR app so it's tied to the employee's personnel file. But the onboarding tasks come from a task-tracking tool with requirements defined by each department, from a different vendor and on a different domain than the HR app. It's on IT to bridge the two. Wiring the two together normally costs the user an OAuth consent screen or costs IT a shared service account. Cross App Access (XAA) removes that step. The company's identity provider vouches for the user across the boundary, under a policy the admin sets in advance. In this tutorial, you'll build that flow end-to-end in TypeScript. You'll build a Model Context Protocol (MCP) requesting app: a web app that signs a user in through an enterprise Identity Provider (IdP), exchanges that identity for a delegation token called an Identity Assertion JWT Authorization Grant (ID-JAG), trades the ID-JAG for an access token, and calls a protected MCP server to fetch real data. You'll use the MCP TypeScript SDK, which added first-class Cross App Access support, and you'll test everything against xaa.dev, the free XAA playground from the Okta Dev Advocacy team. By the end of this post, you can: Explain what XAA is and why AI agents and enterprise apps need it Read an ID-JAG and understand key claims in it Understand each step of the XAA flow through the SDK functions Let the SDK's CrossAppAccessProvider run the whole flow for you Prerequisites Node.js 20 or later npm, which ships with Node.js A free xaa.dev registration (email only) Familiarity with OAuth 2.0 concepts. If Proof Key for Code Exchange (PKCE) is new to you, read Secure Your Express App with OAuth 2.0, OIDC, and PKCE first. The code in this tutorial runs against @modelcontextprotocol/client version 2.0.0-alpha.2, openid-client 6, Express 4, and the xaa.dev playground services. The MCP SDK

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

DevFeed: [Classic Engine Feature EOL: SSR, Desktop SSO, Device Trust](<https://devfeed.tech/articles/classic-engine-feature-eol-ssr-desktop-sso-device-trust-55058.md>)

Original publisher: [Read original article](<https://developer.okta.com/blog/2026/09/18/okta-classic-engine-deprecation>)

Author: Vanshika Pandey

Published: 2026-09-18T05:00:00Z

Content type: release

Language: en

Sources: [Okta Developer](<https://devfeed.tech/sources/okta-developer.md>)

Topics: [okta](<https://devfeed.tech/topics/okta.md>), [identity and access management](<https://devfeed.tech/topics/identity-and-access-management.md>), [Authentication](<https://devfeed.tech/topics/authentication.md>), [Security](<https://devfeed.tech/topics/security.md>), [Device Trust](<https://devfeed.tech/topics/device-trust.md>), [Single sign-on (SSO)](<https://devfeed.tech/topics/sso.md>), [MFA](<https://devfeed.tech/topics/mfa.md>), [upgrade](<https://devfeed.tech/topics/upgrade.md>), [self-service](<https://devfeed.tech/topics/self-service.md>), [passwords](<https://devfeed.tech/topics/passwords.md>), [Zero Trust](<https://devfeed.tech/topics/zero-trust.md>)

Tags: [access-management](<https://devfeed.tech/tags/access-management.md>), [announcement](<https://devfeed.tech/tags/announcement.md>), [authentication](<https://devfeed.tech/tags/authentication.md>), [benefit](<https://devfeed.tech/tags/benefit.md>), [device-trust](<https://devfeed.tech/tags/device-trust.md>), [eol](<https://devfeed.tech/tags/eol.md>), [feature](<https://devfeed.tech/tags/feature.md>), [identity](<https://devfeed.tech/tags/identity.md>), [okta](<https://devfeed.tech/tags/okta.md>), [password](<https://devfeed.tech/tags/password.md>), [passwordless](<https://devfeed.tech/tags/passwordless.md>), [phishing](<https://devfeed.tech/tags/phishing.md>), [policies](<https://devfeed.tech/tags/policies.md>), [security](<https://devfeed.tech/tags/security.md>), [security-vulnerabilities](<https://devfeed.tech/tags/security-vulnerabilities.md>), [self-service](<https://devfeed.tech/tags/self-service.md>), [sign-in](<https://devfeed.tech/tags/sign-in.md>), [sso](<https://devfeed.tech/tags/sso.md>), [upgrade](<https://devfeed.tech/tags/upgrade.md>), [verification](<https://devfeed.tech/tags/verification.md>), [vulnerabilities](<https://devfeed.tech/tags/vulnerabilities.md>)

### AI overview

Okta will end support for Self-Service Registration, Desktop Single Sign-On, and Device Trust on Classic Engine on March 5, 2027. Organizations must upgrade to Okta Identity Engine to retain those capabilities. Identity Engine provides passwordless authentication, device assurance, phishing-resistant multifactor authentication, and updated security policies.

### Source excerpt

Starting March 5, 2027, Okta ends support for a few capabilities on Classic Engine. Identity and security requirements continue to evolve. Organizations expect authentication experiences that are more secure, flexible, and adaptable to changing users, devices, and applications. Okta invests in Okta Identity Engine, the modern foundation for passwordless authentication, device assurance, phishing-resistant multifactor authentication, and adaptive security policies. By moving to Okta Identity Engine, you access an environment aligned with modern security practices that is stronger, more capable, and built to support how you protect access. What's changing in Okta Classic Engine Here's the full list of affected capabilities: Self-Service Registration Desktop Single Sign-On (Integrated Windows Authentication, or IWA) Device Trust Once support ends, Okta turns off these capabilities on Classic Engine, and you lose access to them unless you upgrade to Okta Identity Engine first. Okta no longer addresses bugs, security vulnerabilities, or broken flows associated with them after that date. Each capability moves to a modern, more secure approach within Identity Engine, where it continues to benefit from ongoing innovation. Why upgrade to Okta Identity Engine Identity Engine gives you authentication capabilities Classic Engine doesn't have, including passwordless authentication, device assurance, and a modernized policy framework built on a newer authentication pipeline. The upgrade itself is free, you get all these capabilities at no additional licensing cost as part of your existing Okta subscription. Identity Engine accelerates five core use cases: Passwordless: Remove password from the sign-in flow entirely, instead of layering a second factor on top of it Phishing-resistant: Close every route to the account, not just the front door. An account is only as phishing-resistant as its weakest enrollment and recovery path. ID verification : Confirm that employees and customers

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

DevFeed: [Classic Engine Feature EOL: SSR, Desktop SSO, Device Trust](<https://devfeed.tech/articles/classic-engine-feature-eol-ssr-desktop-sso-device-trust-133758.md>)

Original publisher: [Read original article](<https://developer.okta.com/blog/2026/09/18/okta-classic-engine-deprecation/>)

Author: Vanshika Pandey

Published: 2026-09-18T00:00:00Z

Content type: release

Language: en

Sources: [Okta Developer](<https://devfeed.tech/sources/okta-developer.md>)

Topics: [okta](<https://devfeed.tech/topics/okta.md>), [Device Trust](<https://devfeed.tech/topics/device-trust.md>), [Single sign-on (SSO)](<https://devfeed.tech/topics/sso.md>), [Zero Trust](<https://devfeed.tech/topics/zero-trust.md>)

Tags: [3](<https://devfeed.tech/tags/3.md>), [about](<https://devfeed.tech/tags/about.md>), [access-management](<https://devfeed.tech/tags/access-management.md>), [account](<https://devfeed.tech/tags/account.md>), [announcement](<https://devfeed.tech/tags/announcement.md>), [desktop](<https://devfeed.tech/tags/desktop.md>), [device](<https://devfeed.tech/tags/device.md>), [device-trust](<https://devfeed.tech/tags/device-trust.md>), [end-of-support](<https://devfeed.tech/tags/end-of-support.md>), [engine](<https://devfeed.tech/tags/engine.md>), [eol](<https://devfeed.tech/tags/eol.md>), [feature](<https://devfeed.tech/tags/feature.md>), [identity](<https://devfeed.tech/tags/identity.md>), [okta](<https://devfeed.tech/tags/okta.md>), [self-service](<https://devfeed.tech/tags/self-service.md>), [service](<https://devfeed.tech/tags/service.md>), [sso](<https://devfeed.tech/tags/sso.md>), [ssr](<https://devfeed.tech/tags/ssr.md>), [support](<https://devfeed.tech/tags/support.md>), [trust](<https://devfeed.tech/tags/trust.md>), [upgrade](<https://devfeed.tech/tags/upgrade.md>)

### AI overview

Starting March 5, 2027, Okta will turn off Self-Service Registration, Desktop SSO using IWA, and Device Trust on Classic Engine, and will stop fixing related bugs, vulnerabilities, and broken flows. The excerpt maps these features to Identity Engine alternatives: Profile Enrollment Policy for self-service registration; Agentless Desktop SSO or Okta FastPass for IWA, with the choice depending on authentication and device management strategy; and management attestation with Okta Verify for Device Trust. The Identity Engine upgrade is described as free under existing subscriptions, but not every Classic Engine feature carries over, and replacement availability may vary. Okta recommends assessing current configuration and feature use, testing in a non-production environment, and planning the production upgrade before the deadline with help from its account or upgrade teams.

### Source excerpt

Okta Classic Engine's Self-Service Registration, Desktop SSO, and Device Trust reach end of support - upgrade to Identity Engine now.

## Build an Authenticated Standalone Angular v22 App with the Okta Angular SDK

DevFeed: [Build an Authenticated Standalone Angular v22 App with the Okta Angular SDK](<https://devfeed.tech/articles/supercharge-auth-with-signals-and-the-new-okta-angular-sdk-15977.md>)

Original publisher: [Read original article](<https://developer.okta.com/blog/2026/08/25/angular-auth-signals>)

Author: Alisa Duncan

Published: 2026-08-25T05:00:00Z

Content type: tutorial

Language: en

Sources: [Okta Developer](<https://devfeed.tech/sources/okta-developer.md>)

Topics: [Angular](<https://devfeed.tech/topics/angular.md>), [Authentication](<https://devfeed.tech/topics/authentication.md>), [OpenID connect (OIDC)](<https://devfeed.tech/topics/oidc.md>), [Angular CLI](<https://devfeed.tech/topics/angular-cli.md>), [OAuth](<https://devfeed.tech/topics/oauth.md>), [SDK](<https://devfeed.tech/topics/sdk.md>), [Node.js](<https://devfeed.tech/topics/node-js.md>)

Tags: [angular](<https://devfeed.tech/tags/angular.md>), [angular-v22](<https://devfeed.tech/tags/angular-v22.md>), [authentication](<https://devfeed.tech/tags/authentication.md>), [cli](<https://devfeed.tech/tags/cli.md>), [node-js](<https://devfeed.tech/tags/node-js.md>), [oauth](<https://devfeed.tech/tags/oauth.md>), [oidc](<https://devfeed.tech/tags/oidc.md>), [release](<https://devfeed.tech/tags/release.md>), [sdk](<https://devfeed.tech/tags/sdk.md>), [tutorial](<https://devfeed.tech/tags/tutorial.md>)

### AI overview

This tutorial updates a small Angular v22 application to use the standalone Okta Angular SDK. It covers adding authentication with the provider function, protecting routes with functional guards, loading user groups with rxResource and signal inputs, and moving Okta configuration to runtime loading.

### Source excerpt

Have you noticed that the Okta Angular SDK went fully standalone? There's no NgModule left to import, no importProvidersFrom wrapper to remember, and the guards are plain functions now. If you've been waiting for the SDK to look like the rest of your standalone Angular app, this is the release you were waiting for. In this post, we'll pick up a small Angular v22 project and finish it. We'll make the following changes: Add authentication using the new provideOktaAuth provider function Protect a route with the SDK's functional guard Load each user's groups with rxResource and a signal input Move the Okta configuration to runtime loading We're calling Okta's APIs directly for this project, so we don't have to stand up a separate backend. If you want to jump to the completed project, you can find it in the okta-angular-auth-signals-example GitHub repository. Otherwise, warm up your fingers and let's get coding! Note This post is best for developers familiar with Angular. If you are an Angular newbie, start by building your first Angular app using the tutorial created by the Angular team. Prerequisites For this tutorial, you will need the following tools: Node.js v22 or greater Angular CLI An Okta Integrator Free Plan account A web browser with good debugging capabilities Your favorite IDE Terminal window (if you aren't using an IDE with a built-in terminal) Table of Contents Get the starting Angular project Secure the Angular app with OAuth 2.1 and OpenID Connect (OIDC) using Okta Grant API scopes to read users and groups Allow cross-origin requests and protect the access token Add authentication with the standalone Okta Angular provider Protect routes with functional route guards Add users to your Okta org Display users and review Angular's rxResource API Load a user's groups with rxResource and a signal input Display group details using signal inputs Load your Okta configuration at runtime Learn more about Angular signals, standalone APIs, and OIDC Get the starting An

## Supercharge Auth with Signals and the New Okta Angular SDK

DevFeed: [Supercharge Auth with Signals and the New Okta Angular SDK](<https://devfeed.tech/articles/supercharge-auth-with-signals-and-the-new-okta-angular-sdk-133757.md>)

Original publisher: [Read original article](<https://developer.okta.com/blog/2026/08/25/angular-auth-signals/>)

Author: Alisa Duncan

Published: 2026-08-25T00:00:00Z

Content type: tutorial

Language: en

Sources: [Okta Developer](<https://devfeed.tech/sources/okta-developer.md>)

Topics: [Angular](<https://devfeed.tech/topics/angular.md>), [okta](<https://devfeed.tech/topics/okta.md>), [SDK](<https://devfeed.tech/topics/sdk.md>), [Secure token management](<https://devfeed.tech/topics/secure-token-management.md>)

Tags: [angular](<https://devfeed.tech/tags/angular.md>), [angular-v22](<https://devfeed.tech/tags/angular-v22.md>), [auth](<https://devfeed.tech/tags/auth.md>), [authentication](<https://devfeed.tech/tags/authentication.md>), [oidc](<https://devfeed.tech/tags/oidc.md>), [okta](<https://devfeed.tech/tags/okta.md>), [sdk](<https://devfeed.tech/tags/sdk.md>)

### AI overview

The article shows how to add Okta authentication to a standalone Angular app using the newer provider and functional guard APIs, then load each user's groups reactively. It configures an OIDC single-page app with the org authorization server and the `okta.users.read` scope, enables DPoP, and uses `provideOktaAuth()` plus `canActivateAuthGuard` to protect the dashboard. For group data, `rxResource` tracks a required signal input and refetches when the selected user changes; computed values show the full group count while limiting displayed panels to three. The article also demonstrates loading public issuer and client ID configuration at startup with `provideAppInitializer()` and `fetch`, noting that injection must happen before the first `await`. Its example calls Okta management APIs directly from the browser and cautions that the access token can perform sensitive admin actions.

### Source excerpt

The Okta Angular SDK is standalone-ready! Add authentication to an Angular v22 app and load user groups with signals and rxResource.

## Add Cross App Access to Your OIDC Resource Application

DevFeed: [Add Cross App Access to Your OIDC Resource Application](<https://devfeed.tech/articles/add-cross-app-access-to-your-oidc-resource-application-15976.md>)

Original publisher: [Read original article](<https://developer.okta.com/blog/2026/08/24/xaa-oidc-resource>)

Author: Sohail Pathan

Published: 2026-08-24T05:00:00Z

Content type: tutorial

Language: en

Sources: [Okta Developer](<https://devfeed.tech/sources/okta-developer.md>)

Topics: [OpenID connect (OIDC)](<https://devfeed.tech/topics/oidc.md>), [API](<https://devfeed.tech/topics/api.md>), [Authorization](<https://devfeed.tech/topics/authorization.md>), [JSON Web Tokens](<https://devfeed.tech/topics/jwt.md>), [Single sign-on (SSO)](<https://devfeed.tech/topics/sso.md>), [OAuth 2.0](<https://devfeed.tech/topics/oauth2.md>)

Tags: [api](<https://devfeed.tech/tags/api.md>), [authorization](<https://devfeed.tech/tags/authorization.md>), [cross-app-access](<https://devfeed.tech/tags/cross-app-access.md>), [jwt](<https://devfeed.tech/tags/jwt.md>), [oauth-2-0](<https://devfeed.tech/tags/oauth-2-0.md>), [oidc](<https://devfeed.tech/tags/oidc.md>), [okta](<https://devfeed.tech/tags/okta.md>), [scopes](<https://devfeed.tech/tags/scopes.md>), [sso](<https://devfeed.tech/tags/sso.md>), [token](<https://devfeed.tech/tags/token.md>), [xaa](<https://devfeed.tech/tags/xaa.md>)

### AI overview

This guide explains how OIDC-federated applications can support Cross App Access (XAA) for API access on behalf of users. It covers validating and redeeming the ID-JAG, resolving users from claims, issuing access tokens, updating authorization server metadata, and testing the end-to-end flow.

### Source excerpt

If you currently federate enterprise customers using OpenID Connect (OIDC) and want to allow applications to access your API on behalf of those users, this Cross App Access (XAA) guide is for you. The Identity Assertion Authorization Grant specification, the basis of XAA, was designed with OIDC in mind. Your authorization server already trusts the customer's IdP for single sign-on (SSO), and XAA reuses that same trust for API access. This guide details what you need to support, how to validate the grant, and how to resolve the user at your resource authorization server. Table of Contents How XAA in OIDC works Analyzing the ID-JAG claims XAA implementation checklist for OIDC-federated applications Mapping user identity from iss and sub Validating the ID-JAG and resolving the user Issuing the access token Updating authorization server metadata Making cross-application requests from your OIDC app securely Configure your XAA OIDC Resource app in Okta Create the OIDC requesting app for testing Create the OIDC resource app in Okta Register and configure the AI Agent in Okta Verify your Okta XAA setup on xaa.dev Configure OIDC SSO Verify the refresh token exchange for an ID-JAG token Redeem the ID-JAG for an access token at the resource authorization server Call the resource API with the access token Prove the XAA connection end-to-end Takeaways for implementors who also have SAML apps Learn more about Cross App Access, OIDC, and OAuth 2.0 How XAA in OIDC works When an agent (like one running in Claude) needs API access, it presents an Identity Assertion Authorization Grant (ID-JAG). The ID-JAG is a short-lived JSON Web Token (JWT) issued by the customer's Identity Provider (IdP) for your authorization server. Your resource server accepts the token, identifies the user, and issues your own access token, all while leaving the customer's existing OIDC integration untouched. The sequence diagram shown below describes the OIDC XAA flow. Notice that the OIDC SSO flow stays the

## Add Cross App Access to Your OIDC Resource Application

DevFeed: [Add Cross App Access to Your OIDC Resource Application](<https://devfeed.tech/articles/add-cross-app-access-to-your-oidc-resource-application-133756.md>)

Original publisher: [Read original article](<https://developer.okta.com/blog/2026/08/24/xaa-oidc-resource/>)

Author: Sohail Pathan

Published: 2026-08-24T00:00:00Z

Content type: tutorial

Language: en

Sources: [Okta Developer](<https://devfeed.tech/sources/okta-developer.md>)

Topics: [cross-app-access](<https://devfeed.tech/topics/cross-app-access.md>), [OpenID connect (OIDC)](<https://devfeed.tech/topics/oidc.md>), [Single sign-on (SSO)](<https://devfeed.tech/topics/sso.md>)

Tags: [2](<https://devfeed.tech/tags/2.md>), [3](<https://devfeed.tech/tags/3.md>), [account](<https://devfeed.tech/tags/account.md>), [after](<https://devfeed.tech/tags/after.md>), [agent](<https://devfeed.tech/tags/agent.md>), [agents](<https://devfeed.tech/tags/agents.md>), [ai](<https://devfeed.tech/tags/ai.md>), [ai-agent](<https://devfeed.tech/tags/ai-agent.md>), [app](<https://devfeed.tech/tags/app.md>), [application](<https://devfeed.tech/tags/application.md>), [apps](<https://devfeed.tech/tags/apps.md>), [cross](<https://devfeed.tech/tags/cross.md>), [cross-app-access](<https://devfeed.tech/tags/cross-app-access.md>), [how-to](<https://devfeed.tech/tags/how-to.md>), [oidc](<https://devfeed.tech/tags/oidc.md>), [resource](<https://devfeed.tech/tags/resource.md>), [sso](<https://devfeed.tech/tags/sso.md>), [using](<https://devfeed.tech/tags/using.md>), [with](<https://devfeed.tech/tags/with.md>), [xaa](<https://devfeed.tech/tags/xaa.md>)

### AI overview

An OIDC resource authorization server can support Cross App Access by accepting an IdP-issued, short-lived ID-JAG and exchanging it for its own access token, without changing the existing SSO flow. Bind the token's `iss` to a registered IdP before verifying its signature with that connection's JWKS; then check its type, `aud`, and authenticated client's `client_id`. Resolve users by `iss` + `sub` (also `tenant` for a multi-tenant IdP), using `email` only as a just-in-time provisioning hint. Apply local scope policy and issue an access token without a refresh token; clients can resubmit the ID-JAG until it expires. Publish the JWT bearer grant and `id-jag` profile in authorization server metadata, without listing trusted issuers publicly. The walkthrough uses Okta and xaa.dev to test an already implemented resource server: it requires a reachable issuer and token endpoint, client registration and redemption logic, and an API that accepts the issued token. The resource issuer must match the ID-JAG audience exactly. For SAML connections, the subject instead uses `sub_id` in `saml-nameid` format and is matched by its NameID members; the other redemption rules remain the same.

### Source excerpt

Learn how to secure app-to-app connections using Cross App Access (XAA) with OIDC SSO for OIDC-based resource apps.

## Add Cross App Access to Your OIDC Requesting Application

DevFeed: [Add Cross App Access to Your OIDC Requesting Application](<https://devfeed.tech/articles/add-cross-app-access-to-your-oidc-requesting-application-15975.md>)

Original publisher: [Read original article](<https://developer.okta.com/blog/2026/08/21/xaa-oidc-requesting>)

Author: Sohail Pathan

Published: 2026-08-21T05:00:00Z

Content type: tutorial

Language: en

Sources: [Okta Developer](<https://devfeed.tech/sources/okta-developer.md>)

Topics: [OpenID connect (OIDC)](<https://devfeed.tech/topics/oidc.md>), [OAuth](<https://devfeed.tech/topics/oauth.md>), [OAuth 2.0](<https://devfeed.tech/topics/oauth2.md>), [JSON Web Tokens](<https://devfeed.tech/topics/jwt.md>), [API](<https://devfeed.tech/topics/api.md>), [Authorization](<https://devfeed.tech/topics/authorization.md>), [AI Agent](<https://devfeed.tech/topics/ai-agent.md>)

Tags: [agent](<https://devfeed.tech/tags/agent.md>), [api](<https://devfeed.tech/tags/api.md>), [authorization](<https://devfeed.tech/tags/authorization.md>), [callback](<https://devfeed.tech/tags/callback.md>), [claude](<https://devfeed.tech/tags/claude.md>), [cross-app-access](<https://devfeed.tech/tags/cross-app-access.md>), [identity](<https://devfeed.tech/tags/identity.md>), [jwt](<https://devfeed.tech/tags/jwt.md>), [oauth](<https://devfeed.tech/tags/oauth.md>), [oauth-2-0](<https://devfeed.tech/tags/oauth-2-0.md>), [oidc](<https://devfeed.tech/tags/oidc.md>), [openid-connect](<https://devfeed.tech/tags/openid-connect.md>), [sso](<https://devfeed.tech/tags/sso.md>), [third-party-applications](<https://devfeed.tech/tags/third-party-applications.md>), [token](<https://devfeed.tech/tags/token.md>), [xaa](<https://devfeed.tech/tags/xaa.md>)

### AI overview

This guide explains how an OIDC-federated application can use Cross App Access (XAA) to request resources from a third-party application. It describes exchanging a refresh token for an Identity Assertion Authorization Grant, exchanging that short-lived JWT for an OAuth access token, and using the access token for the resource API request.

### Source excerpt

If you currently federate enterprise customers using OpenID Connect (OIDC) and want to connect with third-party applications, this Cross App Access (XAA) guide is for you. The Identity Assertion Authorization Grant specification, the basis of XAA, was designed with OIDC in mind. Your app already holds an ID token after sign-in, but it's the refresh token from that same sign-in that you exchange to reach a third-party app. This guide details what you need to support and how to make resource requests to a third-party app using XAA. Table of Contents How XAA in OIDC works XAA implementation checklist for OIDC-federated applications Request the ID-JAG token Request the access token Call the resource API Handle token expiration Making cross-application requests from your OIDC app securely Configure your XAA OIDC requesting app in Okta Register the requesting app in Okta Register the test resource app in Okta Register your requesting app at xaa.dev Register and configure the AI Agent in Okta Validate the XAA connection end-to-end Learn more about Cross App Access, OIDC, and OAuth 2.0 How XAA in OIDC works When an agent (like one running in Claude) needs API access, it presents an Identity Assertion Authorization Grant (ID-JAG). The ID-JAG is a short-lived JSON Web Token (JWT) issued by the Identity Provider (IdP) for your app's user. You exchange the ID-JAG token for an access token to the resource application you're connecting with. The sequence diagram below describes the OIDC XAA flow and how your application fits into it. You'll handle the flow in two parts: where your application requests the ID-JAG from the IdP using the refresh token, and where your app requests the access token from the ID-JAG from the third-party resource app's authorization server. XAA implementation checklist for OIDC-federated applications Follow the guide in this section to support XAA in your OIDC application when your app connects to a third-party resource application. The XAA flow places t

## Add Cross App Access to Your OIDC Requesting Application

DevFeed: [Add Cross App Access to Your OIDC Requesting Application](<https://devfeed.tech/articles/add-cross-app-access-to-your-oidc-requesting-application-133755.md>)

Original publisher: [Read original article](<https://developer.okta.com/blog/2026/08/21/xaa-oidc-requesting/>)

Author: Sohail Pathan

Published: 2026-08-21T00:00:00Z

Content type: tutorial

Language: en

Sources: [Okta Developer](<https://devfeed.tech/sources/okta-developer.md>)

Topics: [cross-app-access](<https://devfeed.tech/topics/cross-app-access.md>), [OpenID connect (OIDC)](<https://devfeed.tech/topics/oidc.md>), [Single sign-on (SSO)](<https://devfeed.tech/topics/sso.md>)

Tags: [2](<https://devfeed.tech/tags/2.md>), [3](<https://devfeed.tech/tags/3.md>), [access-tokens](<https://devfeed.tech/tags/access-tokens.md>), [account](<https://devfeed.tech/tags/account.md>), [after](<https://devfeed.tech/tags/after.md>), [agent](<https://devfeed.tech/tags/agent.md>), [ai](<https://devfeed.tech/tags/ai.md>), [ai-agent](<https://devfeed.tech/tags/ai-agent.md>), [all](<https://devfeed.tech/tags/all.md>), [app](<https://devfeed.tech/tags/app.md>), [application](<https://devfeed.tech/tags/application.md>), [apps](<https://devfeed.tech/tags/apps.md>), [cross](<https://devfeed.tech/tags/cross.md>), [cross-app-access](<https://devfeed.tech/tags/cross-app-access.md>), [enterprise](<https://devfeed.tech/tags/enterprise.md>), [oidc](<https://devfeed.tech/tags/oidc.md>), [sso](<https://devfeed.tech/tags/sso.md>), [using](<https://devfeed.tech/tags/using.md>), [with](<https://devfeed.tech/tags/with.md>), [xaa](<https://devfeed.tech/tags/xaa.md>)

### AI overview

For an OIDC application to call a third-party API through Cross App Access (XAA), retain the refresh token from the usual authorization code sign-in with `offline_access`. Exchange it at Okta's `/token` endpoint, using OAuth 2.0 Token Exchange and the app's client credentials, to obtain a short-lived ID-JAG. Redeem that assertion at the resource app's authorization server using the JWT bearer grant and that server's required client authentication and scopes; use the returned access token for the API call. Request a new ID-JAG with the same refresh token when it expires; if the refresh token expires or is revoked and Okta returns `invalid_grant`, the user must sign in again. The walkthrough configures Okta requester and test resource integrations, enables XAA with the resource authorization server's issuer URL, registers the requester at xaa.dev, and verifies the exchange and API call there. The example's Basic authorization header is illustrative; use the scheme the resource application requires.

### Source excerpt

Secure app-to-app connections using Cross App Access (XAA) with OIDC SSO for OIDC-federated enterprise apps.

## I Found My Coordinates: Code, Community, and Okta

DevFeed: [I Found My Coordinates: Code, Community, and Okta](<https://devfeed.tech/articles/i-found-my-coordinates-code-community-and-okta-15974.md>)

Original publisher: [Read original article](<https://developer.okta.com/blog/2026/08/20/vanshika-intro-blog>)

Author: Vanshika Pandey

Published: 2026-08-20T05:00:00Z

Content type: opinion

Language: en

Sources: [Okta Developer](<https://devfeed.tech/sources/okta-developer.md>)

Topics: [software-development](<https://devfeed.tech/topics/software-development.md>), [Software Engineering](<https://devfeed.tech/topics/software-engineering.md>), [Google](<https://devfeed.tech/topics/google.md>)

Tags: [advocacy](<https://devfeed.tech/tags/advocacy.md>), [community](<https://devfeed.tech/tags/community.md>), [developer](<https://devfeed.tech/tags/developer.md>), [google](<https://devfeed.tech/tags/google.md>), [hackathons](<https://devfeed.tech/tags/hackathons.md>), [javascript](<https://devfeed.tech/tags/javascript.md>), [journey](<https://devfeed.tech/tags/journey.md>), [networking](<https://devfeed.tech/tags/networking.md>), [okta](<https://devfeed.tech/tags/okta.md>), [security](<https://devfeed.tech/tags/security.md>), [work](<https://devfeed.tech/tags/work.md>)

### AI overview

A personal account of developing a career through campus ambassador work, internships, community building, developer advocacy, and software development.

### Source excerpt

It all started with a phone call from an institute that reached out to recruit me for its campus ambassador program. I was navigating my first year of college, figuring things out. It was all new for me, a new city, far from home, and a hostel room. I was not aware of anything except books and lectures. A senior at my campus ambassador program advised me to create a LinkedIn account and start looking for opportunities from day one. As they say, "You don't have to be great to start, but you have to start to be great." So I started applying for random internships. Soon, I received my first offer, where I discovered the power of networking and community. "No one can whistle a symphony. It takes a whole orchestra to play it." - H.E. Luccock Community has always been the best part of my life. The love and support we receive from each other are invaluable. I have always given to the community and gained far more in return. I attended an institution that wasn't particularly well-known. There weren't many communities, so why not do something about it? Through professional platforms, I discovered Google Developer Student Clubs (GDSC), researched the opportunity, and applied. I became the pioneer GDSC Lead at my institution, and one of 280 leads across India. We built the community from scratch, organizing meetups, workshops, and hackathons that delivered real value to students. These experiences sparked curiosity and helped students find their voice. When I stumbled across the Developer Advocate role, I was very happy and curious, so I started digging into it. My journey into advocacy "What you seek is seeking you." - Rumi One day, I got an email from a founder who said he liked my LinkedIn profile and wanted me to join his organization as a Developer Advocate - that moment was surreal. That's how I landed an internship as a Developer Advocate at Zuplo, where I learned something crucial: to understand developers' pain points, I needed to walk in their shoes. To truly advocat

## I Found My Coordinates: Code, Community, and Okta

DevFeed: [I Found My Coordinates: Code, Community, and Okta](<https://devfeed.tech/articles/i-found-my-coordinates-code-community-and-okta-133754.md>)

Original publisher: [Read original article](<https://developer.okta.com/blog/2026/08/20/vanshika-intro-blog/>)

Author: Vanshika Pandey

Published: 2026-08-20T00:00:00Z

Content type: article

Language: en

Sources: [Okta Developer](<https://devfeed.tech/sources/okta-developer.md>)

Topics: [developer-relations](<https://devfeed.tech/topics/developer-relations.md>), [okta](<https://devfeed.tech/topics/okta.md>), [coding-community](<https://devfeed.tech/topics/coding-community.md>), [Developer Events](<https://devfeed.tech/topics/developer-events.md>), [Low code](<https://devfeed.tech/topics/low-code.md>), [X (Twitter)](<https://devfeed.tech/topics/twitter.md>)

Tags: [3](<https://devfeed.tech/tags/3.md>), [about](<https://devfeed.tech/tags/about.md>), [access-management](<https://devfeed.tech/tags/access-management.md>), [account](<https://devfeed.tech/tags/account.md>), [advocacy](<https://devfeed.tech/tags/advocacy.md>), [agents](<https://devfeed.tech/tags/agents.md>), [ai](<https://devfeed.tech/tags/ai.md>), [all](<https://devfeed.tech/tags/all.md>), [also](<https://devfeed.tech/tags/also.md>), [am](<https://devfeed.tech/tags/am.md>), [ambassador](<https://devfeed.tech/tags/ambassador.md>), [applying](<https://devfeed.tech/tags/applying.md>), [articles](<https://devfeed.tech/tags/articles.md>), [award](<https://devfeed.tech/tags/award.md>), [code](<https://devfeed.tech/tags/code.md>), [community](<https://devfeed.tech/tags/community.md>), [found](<https://devfeed.tech/tags/found.md>), [i](<https://devfeed.tech/tags/i.md>), [javascript](<https://devfeed.tech/tags/javascript.md>), [my](<https://devfeed.tech/tags/my.md>), [okta](<https://devfeed.tech/tags/okta.md>), [security](<https://devfeed.tech/tags/security.md>)

### AI overview

Vanshika describes how campus community work and developer experience led to her joining Okta as a Senior Builder Advocate. She began by building a Google Developer Student Clubs chapter at her institution, then worked as a Developer Advocate intern at Zuplo and as a Software Development Engineer at JPMorgan, saying that hands-on development helped her understand developers' challenges. She reports delivering sessions at Indian colleges, mentoring more than 10,000 students, and building a community of over 600,000 tech enthusiasts. At Okta, she intends to bring that community and advocacy experience to builders broadly, including AI, no-code and low-code builders as well as developers, in support of Okta's mission to secure every interaction.

### Source excerpt

Vanshika joins the Okta team!

## Build a Flask App with Okta for Secure OIDC Login and Authorized API Calls

DevFeed: [Build a Flask App with Okta for Secure OIDC Login and Authorized API Calls](<https://devfeed.tech/articles/build-a-flask-app-with-okta-for-secure-oidc-login-and-authorized-api-calls-15973.md>)

Original publisher: [Read original article](<https://developer.okta.com/blog/2026/07/28/flask-oauth-web-app>)

Author: Akanksha Bhasin

Published: 2026-07-28T05:00:00Z

Content type: tutorial

Language: en

Sources: [Okta Developer](<https://devfeed.tech/sources/okta-developer.md>)

Topics: [Flask](<https://devfeed.tech/topics/flask.md>), [OpenID connect (OIDC)](<https://devfeed.tech/topics/oidc.md>), [Tutorial](<https://devfeed.tech/topics/tutorial.md>), [API](<https://devfeed.tech/topics/api.md>), [Authentication](<https://devfeed.tech/topics/authentication.md>), [Authorization](<https://devfeed.tech/topics/authorization.md>), [OAuth 2.0](<https://devfeed.tech/topics/oauth2.md>), [Python](<https://devfeed.tech/topics/python.md>), [Web app](<https://devfeed.tech/topics/webapp.md>)

Tags: [api](<https://devfeed.tech/tags/api.md>), [authentication](<https://devfeed.tech/tags/authentication.md>), [authorization](<https://devfeed.tech/tags/authorization.md>), [flask](<https://devfeed.tech/tags/flask.md>), [oauth](<https://devfeed.tech/tags/oauth.md>), [oauth-2-0](<https://devfeed.tech/tags/oauth-2-0.md>), [oidc](<https://devfeed.tech/tags/oidc.md>), [pkce](<https://devfeed.tech/tags/pkce.md>), [python](<https://devfeed.tech/tags/python.md>), [security](<https://devfeed.tech/tags/security.md>), [tutorial](<https://devfeed.tech/tags/tutorial.md>), [web-app](<https://devfeed.tech/tags/web-app.md>)

### AI overview

This tutorial explains how to build a Flask dashboard that uses Okta OpenID Connect for user sign-in and OAuth 2.0 access tokens to call a protected backend API. It also covers PKCE, custom scopes, self-service registration, and validating scopes to control API responses.

### Source excerpt

Python syntax and the flexibility of the Flask microframework make it a popular choice for quickly building web applications. While Flask provides the essentials to get you started, you'll need to tackle two critical pieces yourself: secure user authentication and authorization for your backend services. After all, how do you securely sign users into your application? And once they're signed in, how does your app fetch data from a backend service that only serves authorized requests? This tutorial shows you how to solve both. You'll build a Flask dashboard app that signs users in with Okta using OpenID Connect (OIDC). Once signed in, the app uses the resulting OAuth 2.0 access token to call a separate backend API that responds only to authorized requests. In this common pattern, a web app needs to fetch data from a protected backend service. You'll use Authlib, an OIDC client library, to configure the Authorization Code flow with Proof Key for Code Exchange (PKCE) automatically. You'll also learn how to add a custom scope to the access token and validate it on the backend to control what data the API returns. Check out the complete source code on GitHub and get started without setting it up from scratch. Table of Contents Build a Flask app with OIDC authentication Create an app integration in the Okta Admin Console Enable self-service user registration Add secure user login to a Flask application with Okta Create a basic Flask web application Configure Flask environment variables Implement the OIDC authentication logic Run the Flask OAuth web app Call a protected API with OAuth scoped tokens Build a protected users API Extend the Flask app to interact with the resource server Update the Flask UI to display protected data Test the protected API integration Learn more about OAuth and OIDC Build a Flask app with OIDC authentication In this tutorial, you'll build a simple dashboard application and learn how to: Securely sign users in to view their profile information us

## Build a Flask App with Okta for Secure OIDC Login and Authorized API Calls

DevFeed: [Build a Flask App with Okta for Secure OIDC Login and Authorized API Calls](<https://devfeed.tech/articles/build-a-flask-app-with-okta-for-secure-oidc-login-and-authorized-api-calls-133753.md>)

Original publisher: [Read original article](<https://developer.okta.com/blog/2026/07/28/flask-oauth-web-app/>)

Author: Akanksha Bhasin

Published: 2026-07-28T00:00:00Z

Content type: tutorial

Language: en

Sources: [Okta Developer](<https://devfeed.tech/sources/okta-developer.md>)

Topics: [OpenID connect (OIDC)](<https://devfeed.tech/topics/oidc.md>), [okta](<https://devfeed.tech/topics/okta.md>), [API](<https://devfeed.tech/topics/api.md>), [client library](<https://devfeed.tech/topics/client-library.md>), [Single sign-on (SSO)](<https://devfeed.tech/topics/sso.md>)

Tags: [api](<https://devfeed.tech/tags/api.md>), [authentication](<https://devfeed.tech/tags/authentication.md>), [authlib](<https://devfeed.tech/tags/authlib.md>), [flask](<https://devfeed.tech/tags/flask.md>), [login](<https://devfeed.tech/tags/login.md>), [oauth](<https://devfeed.tech/tags/oauth.md>), [oidc](<https://devfeed.tech/tags/oidc.md>), [okta](<https://devfeed.tech/tags/okta.md>), [pkce](<https://devfeed.tech/tags/pkce.md>), [python](<https://devfeed.tech/tags/python.md>)

### AI overview

The tutorial builds a Flask dashboard that signs users in through Okta OIDC and uses the resulting access token to call a separate protected API. Authlib handles the Authorization Code flow with PKCE; the app stores user information and tokens in the Flask session and can request a custom `api:read-users` scope. The resource server checks the token's issuer, audience, client ID, and required scope before returning sample users, with 401 responses for missing or invalid tokens and 403 for insufficient scope. The guide also covers Okta app and authorization-server setup, optional self-service registration configuration, environment-based credential storage, and running the app and API locally. It lists Python 3.14 or later and an Okta Integrator Free Plan as prerequisites.

### Source excerpt

Learn to add OIDC login and make authorized API calls in a Flask app using Okta and Authlib library.

## Enable Your SAML Requesting App for Cross App Access

DevFeed: [Enable Your SAML Requesting App for Cross App Access](<https://devfeed.tech/articles/enable-your-saml-requesting-app-for-cross-app-access-15972.md>)

Original publisher: [Read original article](<https://developer.okta.com/blog/2026/07/17/xaa-saml-requester>)

Author: Alisa Duncan

Published: 2026-07-17T05:00:00Z

Content type: tutorial

Language: en

Sources: [Okta Developer](<https://devfeed.tech/sources/okta-developer.md>)

Topics: [OAuth 2.0](<https://devfeed.tech/topics/oauth2.md>), [Authorization](<https://devfeed.tech/topics/authorization.md>), [JSON Web Tokens](<https://devfeed.tech/topics/jwt.md>), [OpenID connect (OIDC)](<https://devfeed.tech/topics/oidc.md>), [API](<https://devfeed.tech/topics/api.md>), [AI Agent](<https://devfeed.tech/topics/ai-agent.md>)

Tags: [api](<https://devfeed.tech/tags/api.md>), [authorization](<https://devfeed.tech/tags/authorization.md>), [claude](<https://devfeed.tech/tags/claude.md>), [cross-app-access](<https://devfeed.tech/tags/cross-app-access.md>), [digital-signature](<https://devfeed.tech/tags/digital-signature.md>), [identity](<https://devfeed.tech/tags/identity.md>), [idp](<https://devfeed.tech/tags/idp.md>), [implementation](<https://devfeed.tech/tags/implementation.md>), [jwt](<https://devfeed.tech/tags/jwt.md>), [oauth](<https://devfeed.tech/tags/oauth.md>), [oauth-2-0](<https://devfeed.tech/tags/oauth-2-0.md>), [oidc](<https://devfeed.tech/tags/oidc.md>), [openid-connect](<https://devfeed.tech/tags/openid-connect.md>), [payload](<https://devfeed.tech/tags/payload.md>), [saml](<https://devfeed.tech/tags/saml.md>), [signing](<https://devfeed.tech/tags/signing.md>), [sso](<https://devfeed.tech/tags/sso.md>), [xaa](<https://devfeed.tech/tags/xaa.md>)

### AI overview

This guide explains how SAML-federated applications can use Cross App Access (XAA) to connect to third-party applications without migrating to OpenID Connect. It covers exchanging a SAML assertion for an OAuth refresh token, an ID-JAG, and an access token, along with token validation and Okta configuration.

### Source excerpt

If you currently federate enterprise customers using Security Assertion Markup Language (SAML) and want to connect with third-party applications without migrating to OpenID Connect (OIDC), this Cross App Access (XAA) guide is for you. The Identity Assertion Authorization Grant specification, the basis of XAA, was originally designed with OIDC in mind. To use it in SAML applications, you must accommodate specific security and uniqueness requirements. This guide details what you need to support and how to make resource requests to a third-party app using XAA. Table of Contents How XAA in SAML works XAA implementation checklist for SAML-federated applications Request the refresh token Request the ID-JAG token Request the access token Handle token expiration Making cross-application requests from your SAML app securely Configure your XAA SAML Requesting App in Okta Register and configure the AI Agent in Okta Test the SAML 2.0 app Validate the XAA connection end-to-end Learn more about Cross App Access, SAML, and OAuth 2.0 How XAA in SAML works When an agent (like one running in Claude) needs API access, it presents an Identity Assertion Authorization Grant (ID-JAG). The ID-JAG is a short-lived JSON Web Token (JWT) issued by the Identity Provider (IdP) for your app's user. You exchange the ID-JAG token for an access token to the resource application you're connecting with. The sequence diagram shown below describes the SAML XAA flow and how your application fits in. You'll handle the flow in two parts: where your application requests the ID-JAG from the IdP using a refresh token, and where your app requests the access token from the ID-JAG from the third-party resource app's authorization server. XAA implementation checklist for SAML-federated applications Follow the guide in this section to support XAA in your SAML application when your app connects to a third-party resource application. The XAA flow places the burden of token validation onto the IdP and the resource ap

## Enable Your SAML Requesting App for Cross App Access

DevFeed: [Enable Your SAML Requesting App for Cross App Access](<https://devfeed.tech/articles/enable-your-saml-requesting-app-for-cross-app-access-133752.md>)

Original publisher: [Read original article](<https://developer.okta.com/blog/2026/07/17/xaa-saml-requester/>)

Author: Alisa Duncan

Published: 2026-07-17T00:00:00Z

Content type: tutorial

Language: en

Sources: [Okta Developer](<https://devfeed.tech/sources/okta-developer.md>)

Topics: [cross-app-access](<https://devfeed.tech/topics/cross-app-access.md>), [saml](<https://devfeed.tech/topics/saml.md>), [Single sign-on (SSO)](<https://devfeed.tech/topics/sso.md>), [okta](<https://devfeed.tech/topics/okta.md>)

Tags: [ai-agent](<https://devfeed.tech/tags/ai-agent.md>), [api-access](<https://devfeed.tech/tags/api-access.md>), [cross-app-access](<https://devfeed.tech/tags/cross-app-access.md>), [enterprise](<https://devfeed.tech/tags/enterprise.md>), [saml](<https://devfeed.tech/tags/saml.md>), [sso](<https://devfeed.tech/tags/sso.md>), [xaa](<https://devfeed.tech/tags/xaa.md>)

### AI overview

A SAML app can use Okta Cross App Access (XAA) without migrating to OIDC by exchanging credentials in three stages: after validating the SAML response, exchange its XML assertion for a long-lived refresh token; use that token to obtain a short-lived ID-JAG from Okta for the resource app's issuer, API URL, and scopes; then redeem the ID-JAG at the resource app's authorization server for an access token. The first two exchanges require a private-key JWT client assertion; the final server uses its required client authentication scheme. Persist the refresh token for the session, never retain the SAML assertion, and obtain a new ID-JAG when it expires. If the refresh token expires and Okta returns `invalid_grant`, the user must sign in through SSO again. The guide also walks through configuring Okta's requester and resource SAML apps, enabling XAA, registering an AI agent and resource connection, and checking the flow with xaa.dev. XAA is described as an early access feature.

### Source excerpt

Secure app-to-app connections using Cross App Access (XAA) with SAML SSO for SAML-based enterprise apps.

## Build a Secure C# MCP App with Cross App Access (XAA)

DevFeed: [Build a Secure C# MCP App with Cross App Access (XAA)](<https://devfeed.tech/articles/build-a-secure-c-mcp-app-with-cross-app-access-xaa-15971.md>)

Original publisher: [Read original article](<https://developer.okta.com/blog/2026/07/16/csharp-mcp-cross-app-access>)

Author: Aasawari Sahasrabuddhe

Published: 2026-07-16T05:00:00Z

Content type: tutorial

Language: en

Sources: [Okta Developer](<https://devfeed.tech/sources/okta-developer.md>)

Topics: [cross-app-access](<https://devfeed.tech/topics/cross-app-access.md>), [Model Context Protocol](<https://devfeed.tech/topics/model-context-protocol.md>), [SDK](<https://devfeed.tech/topics/sdk.md>), [Single sign-on (SSO)](<https://devfeed.tech/topics/sso.md>), [OpenID connect (OIDC)](<https://devfeed.tech/topics/oidc.md>), [MSP MCP](<https://devfeed.tech/topics/msp-mcp.md>), [AI Bots](<https://devfeed.tech/topics/ai-bots.md>), [Tool](<https://devfeed.tech/topics/tool.md>)

Tags: [agent](<https://devfeed.tech/tags/agent.md>), [agents](<https://devfeed.tech/tags/agents.md>), [ai](<https://devfeed.tech/tags/ai.md>), [ai-agents](<https://devfeed.tech/tags/ai-agents.md>), [api](<https://devfeed.tech/tags/api.md>), [app](<https://devfeed.tech/tags/app.md>), [application](<https://devfeed.tech/tags/application.md>), [applications](<https://devfeed.tech/tags/applications.md>), [bearer](<https://devfeed.tech/tags/bearer.md>), [bearer-token](<https://devfeed.tech/tags/bearer-token.md>), [build](<https://devfeed.tech/tags/build.md>), [building](<https://devfeed.tech/tags/building.md>), [but](<https://devfeed.tech/tags/but.md>), [c-sharp](<https://devfeed.tech/tags/c-sharp.md>), [client](<https://devfeed.tech/tags/client.md>), [cross](<https://devfeed.tech/tags/cross.md>), [cross-app-access](<https://devfeed.tech/tags/cross-app-access.md>), [csharp](<https://devfeed.tech/tags/csharp.md>), [mcp](<https://devfeed.tech/tags/mcp.md>), [oauth](<https://devfeed.tech/tags/oauth.md>), [oidc](<https://devfeed.tech/tags/oidc.md>), [with](<https://devfeed.tech/tags/with.md>), [xaa](<https://devfeed.tech/tags/xaa.md>)

### AI overview

Cross App Access (XAA) lets an AI agent carry a user's identity to downstream services under enterprise policy without another login. The described flow uses RFC 8693 for the app to exchange an OIDC ID token with the enterprise Identity Provider for a JWT Authorization Grant (JAG), then RFC 7523 for presenting that JAG to the MCP authorization server to obtain a scoped access token. The article excerpt says it will implement the flow with a C# MCP SDK and test it using an XAA playground, but does not include those implementation steps.

### Source excerpt

A few years ago, getting a user signed in to an application or multiple applications with Single Sign-On (SSO) was enough; OpenID Connect (OIDC) handled the login, JWTs carried the claims, and Proof Key for Code Exchange (PKCE) made it secure. Today, with evolving AI, agents act on behalf of users and seek multiple accesses across different resources to execute a task. And that is when you'll hit the gap. The user has an identity, but the downstream service--like a Model Context Protocol (MCP) server, an API, or an agent tool has no way to trust it: the ID Token that proves the user's identity for your app, not for that service. You need a way to take that identity and have it trusted further down the chain, in line with the org's policy, without asking the user to log in again. Cross App Access (XAA) solves exactly that. The user authenticates once. The Identity Provider (IdP) evaluates the enterprise policy and issues a signed Identity Assertion. The downstream service exchanges that assertion for a scoped Bearer token. In this post, we'll explore how Cross App Access (XAA) closes the trust gap, test the flow using an XAA playground, and implement a secure MCP client in just a few lines of C# using our dedicated SDK. Table of Contents What is Cross App Access (XAA)? Implementing XAA with the C# MCP SDK Building the OIDC flow Automate XAA token exchange with C# SDK Connect the MCP client to the server Testing your C# MCP app with xaa.dev Run your C# MCP app with xaa.dev Learn More About Secure AI Agent Development with C# and MCP What is Cross App Access (XAA)? Before we start implementing and building the application, it is important to understand the mechanics of Cross App Access (XAA). At its core, XAA is an open standard that securely enables AI agents to act on behalf of a user and communicate with downstream applications without requiring constant, manual user consent. While the flow is sophisticated, it relies on two standard interactions: RFC 8693 (Token Exc

## Build a Secure C# MCP App with Cross App Access (XAA)

DevFeed: [Build a Secure C# MCP App with Cross App Access (XAA)](<https://devfeed.tech/articles/build-a-secure-c-mcp-app-with-cross-app-access-xaa-133751.md>)

Original publisher: [Read original article](<https://developer.okta.com/blog/2026/07/16/csharp-mcp-cross-app-access/>)

Author: Aasawari Sahasrabuddhe

Published: 2026-07-16T00:00:00Z

Content type: tutorial

Language: en

Sources: [Okta Developer](<https://devfeed.tech/sources/okta-developer.md>)

Topics: [cross-app-access](<https://devfeed.tech/topics/cross-app-access.md>), [AI Bots](<https://devfeed.tech/topics/ai-bots.md>), [Single sign-on (SSO)](<https://devfeed.tech/topics/sso.md>), [Secure token management](<https://devfeed.tech/topics/secure-token-management.md>)

Tags: [agents](<https://devfeed.tech/tags/agents.md>), [ai](<https://devfeed.tech/tags/ai.md>), [ai-agents](<https://devfeed.tech/tags/ai-agents.md>), [api](<https://devfeed.tech/tags/api.md>), [asp-net](<https://devfeed.tech/tags/asp-net.md>), [asp-net-core](<https://devfeed.tech/tags/asp-net-core.md>), [authentication](<https://devfeed.tech/tags/authentication.md>), [authorization](<https://devfeed.tech/tags/authorization.md>), [bearer](<https://devfeed.tech/tags/bearer.md>), [bearer-token](<https://devfeed.tech/tags/bearer-token.md>), [building](<https://devfeed.tech/tags/building.md>), [c-sharp](<https://devfeed.tech/tags/c-sharp.md>), [client](<https://devfeed.tech/tags/client.md>), [cross-app-access](<https://devfeed.tech/tags/cross-app-access.md>), [csharp](<https://devfeed.tech/tags/csharp.md>), [exchange](<https://devfeed.tech/tags/exchange.md>), [how-to](<https://devfeed.tech/tags/how-to.md>), [mcp](<https://devfeed.tech/tags/mcp.md>), [net](<https://devfeed.tech/tags/net.md>), [oauth](<https://devfeed.tech/tags/oauth.md>), [oidc](<https://devfeed.tech/tags/oidc.md>), [token-exchange](<https://devfeed.tech/tags/token-exchange.md>), [xaa](<https://devfeed.tech/tags/xaa.md>)

### AI overview

Cross App Access (XAA) lets a C# app use a signed identity assertion to obtain scoped access to an MCP server on a user's behalf, without another login. The article describes two exchanges: RFC 8693 exchanges the user's OIDC ID token for a short-lived JWT Authorization Grant at the enterprise identity provider; RFC 7523 exchanges that grant at the MCP authorization server for a scoped access token. The C# MCP SDK's `IdentityAssertionGrantProvider` wraps both exchanges. The example configures ASP.NET Core OIDC with PKCE, passes the session ID token through `IdTokenCallback`, and uses the resulting bearer token with `HttpClientTransport` to initialize an MCP client and read resources. For testing, register the requester app and ToDo MCP resource at xaa.dev, configure the supplied client credentials and endpoints, then run the sample locally. The excerpt presents xaa.dev as a ready-made test environment.

### Source excerpt

Learn how to build a secure C# MCP client using Cross App Access (XAA) and token exchange so AI agents can securely act on behalf of users.

## Okta Launches Journeys, Curated Documentation Guides for Developer Projects

DevFeed: [Okta Launches Journeys, Curated Documentation Guides for Developer Projects](<https://devfeed.tech/articles/introducing-okta-journeys-a-better-way-for-developers-to-learn-identity-15970.md>)

Original publisher: [Read original article](<https://developer.okta.com/blog/2026/07/07/okta-journeys-for-developers>)

Author: Dan Maharry

Published: 2026-07-07T05:00:00Z

Content type: release

Language: en

Sources: [Okta Developer](<https://devfeed.tech/sources/okta-developer.md>)

Topics: [Documentation](<https://devfeed.tech/topics/documentation.md>), [Learning](<https://devfeed.tech/topics/learning.md>), [SDK](<https://devfeed.tech/topics/sdk.md>)

Tags: [announce](<https://devfeed.tech/tags/announce.md>), [apis](<https://devfeed.tech/tags/apis.md>), [configuration](<https://devfeed.tech/tags/configuration.md>), [deployment](<https://devfeed.tech/tags/deployment.md>), [developers](<https://devfeed.tech/tags/developers.md>), [docs](<https://devfeed.tech/tags/docs.md>), [documentation](<https://devfeed.tech/tags/documentation.md>), [learning](<https://devfeed.tech/tags/learning.md>), [migration](<https://devfeed.tech/tags/migration.md>), [sdks](<https://devfeed.tech/tags/sdks.md>)

### AI overview

Okta announces Journeys, curated end-to-end documentation guides for small-to-medium-sized development projects. Each Journey combines learning identity foundations, planning implementation decisions, and building identity solutions.

### Source excerpt

Learning identity management is hard enough. Navigating Okta's documentation to build something shouldn't be. If you've ever lost an afternoon stitching together how-to guides, product docs, and scattered blog posts just to figure out where to start, you're not alone - and we've heard you, loudly and repeatedly. Today, we're excited to announce the official launch of Journeys: a new way to navigate Okta documentation built around the tasks you're actually trying to accomplish. What are Okta Journeys for developers? A Journey is a curated, expert-driven, end-to-end guide built around a small-to-medium-sized development project. Rather than sending you to find a single document and piece the rest together yourself, each Journey walks you through the entire project, from foundational concepts to completion. Journeys address the most frequent questions we've heard from developers. Every Journey includes both brand-new material and revised content to ensure that what you're reading is accurate, up to date, and genuinely useful. Each Journey organizes content into three main sections. Learn identity foundations Before you write a single line of code, it helps to know the terrain. The Learn section anchors the broad "identity" concept, covering foundational knowledge including Okta features, software development kits (SDKs), and application programming interfaces (APIs) relevant to your task. Whether you're new to Okta or just unfamiliar with a specific area, this section gives you the vocabulary and mental model you need to make informed decisions. It ensures you're not just following steps, but truly understanding the technology and concepts underlying your project. Plan your customer identity implementation Good implementations start with good planning. The Plan section walks you through the key decision points to consider before you begin - from the pros and cons of migration strategies and deployment models to configuration options, rate limits, and key performance in

## Introducing Okta Journeys: A Better Way for Developers to Learn Identity

DevFeed: [Introducing Okta Journeys: A Better Way for Developers to Learn Identity](<https://devfeed.tech/articles/introducing-okta-journeys-a-better-way-for-developers-to-learn-identity-133750.md>)

Original publisher: [Read original article](<https://developer.okta.com/blog/2026/07/07/okta-journeys-for-developers/>)

Author: Dan Maharry

Published: 2026-07-07T00:00:00Z

Content type: release

Language: en

Sources: [Okta Developer](<https://devfeed.tech/sources/okta-developer.md>)

Topics: [Learning](<https://devfeed.tech/topics/learning.md>), [okta](<https://devfeed.tech/topics/okta.md>), [identity and access management](<https://devfeed.tech/topics/identity-and-access-management.md>)

Tags: [agents](<https://devfeed.tech/tags/agents.md>), [announcements](<https://devfeed.tech/tags/announcements.md>), [api](<https://devfeed.tech/tags/api.md>), [apis](<https://devfeed.tech/tags/apis.md>), [application-programming-interfaces](<https://devfeed.tech/tags/application-programming-interfaces.md>), [authentication](<https://devfeed.tech/tags/authentication.md>), [branding](<https://devfeed.tech/tags/branding.md>), [build](<https://devfeed.tech/tags/build.md>), [customer-identity](<https://devfeed.tech/tags/customer-identity.md>), [developer](<https://devfeed.tech/tags/developer.md>), [developers](<https://devfeed.tech/tags/developers.md>), [developing](<https://devfeed.tech/tags/developing.md>), [development](<https://devfeed.tech/tags/development.md>), [docs](<https://devfeed.tech/tags/docs.md>), [documentation](<https://devfeed.tech/tags/documentation.md>), [for-developers](<https://devfeed.tech/tags/for-developers.md>), [guides](<https://devfeed.tech/tags/guides.md>), [identity](<https://devfeed.tech/tags/identity.md>), [identity-management](<https://devfeed.tech/tags/identity-management.md>), [learn](<https://devfeed.tech/tags/learn.md>), [okta](<https://devfeed.tech/tags/okta.md>)

### AI overview

Okta Journeys are curated, expert-driven guides that take developers through a small-to-medium project from identity fundamentals to implementation. Each Journey has Learn material on relevant Okta features, SDKs, and APIs; Plan guidance on decisions such as migration strategies, deployment models, configuration, rate limits, and KPIs; and an ordered Build collection of implementation resources. They cover Okta's recommended approach and include common alternatives when practical. The first six Journeys target developers building customer-facing Okta Customer Identity portals, including authentication, registration, branding, and user management. Planned topics include AI agents, Okta Integration Network integrations, and migration from Classic Engine to Okta Identity Engine.

### Source excerpt

Okta for developers just got easier. Discover Journeys -- curated, end-to-end guides that help you learn identity management and build faster.

## Build, Test, and Publish a Cross App Access App in the Okta Integration Network

DevFeed: [Build, Test, and Publish a Cross App Access App in the Okta Integration Network](<https://devfeed.tech/articles/build-test-and-publish-a-cross-app-access-app-in-the-okta-integration-network-133749.md>)

Original publisher: [Read original article](<https://developer.okta.com/blog/2026/07/06/submit-oin-xaa/>)

Author: Gagan Sikri

Published: 2026-07-06T00:00:00Z

Content type: tutorial

Language: en

Sources: [Okta Developer](<https://devfeed.tech/sources/okta-developer.md>)

Topics: [cross-app-access](<https://devfeed.tech/topics/cross-app-access.md>), [okta](<https://devfeed.tech/topics/okta.md>)

Tags: [api](<https://devfeed.tech/tags/api.md>), [app](<https://devfeed.tech/tags/app.md>), [authorization](<https://devfeed.tech/tags/authorization.md>), [build](<https://devfeed.tech/tags/build.md>), [cross](<https://devfeed.tech/tags/cross.md>), [cross-app-access](<https://devfeed.tech/tags/cross-app-access.md>), [developer](<https://devfeed.tech/tags/developer.md>), [developer-tools](<https://devfeed.tech/tags/developer-tools.md>), [free](<https://devfeed.tech/tags/free.md>), [guide](<https://devfeed.tech/tags/guide.md>), [integration](<https://devfeed.tech/tags/integration.md>), [isv](<https://devfeed.tech/tags/isv.md>), [it](<https://devfeed.tech/tags/it.md>), [mcp](<https://devfeed.tech/tags/mcp.md>), [mcp-server](<https://devfeed.tech/tags/mcp-server.md>), [network](<https://devfeed.tech/tags/network.md>), [oauth](<https://devfeed.tech/tags/oauth.md>), [oin](<https://devfeed.tech/tags/oin.md>), [okta](<https://devfeed.tech/tags/okta.md>), [server](<https://devfeed.tech/tags/server.md>), [sso](<https://devfeed.tech/tags/sso.md>), [test](<https://devfeed.tech/tags/test.md>), [xaa](<https://devfeed.tech/tags/xaa.md>)

### AI overview

Cross App Access (XAA) lets an app request data from another vendor's API for a signed-in enterprise user without static API keys or a separate consent prompt for each connection. The flow involves a requesting app exchanging an identity assertion for an Identity Assertion Authorization Grant (ID-JAG), a resource app validating it and issuing a scoped access token, and an identity provider such as Okta handling authentication, policy evaluation, and ID-JAG validation. To implement XAA, developers need an Okta Integrator Free Plan org and must identify their app's XAA role (requesting app, resource app, or both) and SSO protocol (OIDC, SAML, or both); MCP clients are requesting apps and MCP servers are resource apps in the described use cases. They then follow the implementation guide matching role and protocol, test with Okta's developer tools, and submit through the OIN Wizard from the same org. An OIN listing is free and must cover both SSO and XAA. Okta's initial review takes about one business week, with publication shortly afterward.

### Source excerpt

Build Cross App Access into your app or MCP server, test it with Okta's developer tools, and publish it free to the Okta Integration Network.

## Enabling Cross App Access for SAML-Based Resource Apps

DevFeed: [Enabling Cross App Access for SAML-Based Resource Apps](<https://devfeed.tech/articles/enabling-cross-app-access-for-saml-based-resource-apps-133748.md>)

Original publisher: [Read original article](<https://developer.okta.com/blog/2026/07/03/cross-app-access-saml/>)

Author: Sohail Pathan

Published: 2026-07-03T00:00:00Z

Content type: tutorial

Language: en

Sources: [Okta Developer](<https://devfeed.tech/sources/okta-developer.md>)

Topics: [cross-app-access](<https://devfeed.tech/topics/cross-app-access.md>), [saml](<https://devfeed.tech/topics/saml.md>), [Single sign-on (SSO)](<https://devfeed.tech/topics/sso.md>)

Tags: [api](<https://devfeed.tech/tags/api.md>), [cross-app-access](<https://devfeed.tech/tags/cross-app-access.md>), [how-to](<https://devfeed.tech/tags/how-to.md>), [resource](<https://devfeed.tech/tags/resource.md>), [saml](<https://devfeed.tech/tags/saml.md>), [sso](<https://devfeed.tech/tags/sso.md>), [xaa](<https://devfeed.tech/tags/xaa.md>)

### AI overview

The guide explains how SAML-based resource apps can support Cross App Access without changing their existing SAML federation. The resource authorization server receives an ID-JAG JWT, binds its issuer to a registered SAML connection before verifying the signature, checks its type, audience and client ID, then resolves the user from `sub_id` in `saml-nameid` format. User matching should include the SAML issuer, NameID and `sp_name_qualifier`; NameID alone may not be unique, and it should not be assumed to be an email. After applying local scope policy, the server issues its own access token and should not issue a refresh token: the client can resubmit the ID-JAG until it expires. The guide also requires advertising the JWT bearer grant and ID-JAG profile in authorization server metadata, and provides an Okta and xaa.dev setup and conformance-testing walkthrough.

### Source excerpt

Learn how to secure app-to-app connections using Cross App Access (XAA) with SAML SSO for SAML-based resource apps.

## The Builder Revolution: Why We're Shifting to Builder Advocacy

DevFeed: [The Builder Revolution: Why We're Shifting to Builder Advocacy](<https://devfeed.tech/articles/the-builder-revolution-why-we-re-shifting-to-builder-advocacy-133747.md>)

Original publisher: [Read original article](<https://developer.okta.com/blog/2026/06/30/builder-revolution/>)

Author: Michael Palermo

Published: 2026-06-30T00:00:00Z

Content type: opinion

Language: en

Sources: [Okta Developer](<https://devfeed.tech/sources/okta-developer.md>)

Topics: [developer-relations](<https://devfeed.tech/topics/developer-relations.md>), [Developer experience](<https://devfeed.tech/topics/developer-experience.md>), [Machine learning](<https://devfeed.tech/topics/machine-learning.md>)

Tags: [2025](<https://devfeed.tech/tags/2025.md>), [2026](<https://devfeed.tech/tags/2026.md>), [advocacy](<https://devfeed.tech/tags/advocacy.md>), [agent](<https://devfeed.tech/tags/agent.md>), [agentic-ai](<https://devfeed.tech/tags/agentic-ai.md>), [agents](<https://devfeed.tech/tags/agents.md>), [ai](<https://devfeed.tech/tags/ai.md>), [ai-agent](<https://devfeed.tech/tags/ai-agent.md>), [ai-agents](<https://devfeed.tech/tags/ai-agents.md>), [ai-projects](<https://devfeed.tech/tags/ai-projects.md>), [ai-tools](<https://devfeed.tech/tags/ai-tools.md>), [analyst](<https://devfeed.tech/tags/analyst.md>), [apis](<https://devfeed.tech/tags/apis.md>), [automate](<https://devfeed.tech/tags/automate.md>), [automation](<https://devfeed.tech/tags/automation.md>), [aws](<https://devfeed.tech/tags/aws.md>), [builder](<https://devfeed.tech/tags/builder.md>), [builder-advocacy](<https://devfeed.tech/tags/builder-advocacy.md>), [developer-advocacy](<https://devfeed.tech/tags/developer-advocacy.md>), [developers](<https://devfeed.tech/tags/developers.md>), [low-code](<https://devfeed.tech/tags/low-code.md>), [no-code](<https://devfeed.tech/tags/no-code.md>), [okta](<https://devfeed.tech/tags/okta.md>)

### AI overview

Okta renamed Developer Advocacy to Builder Advocacy and Developer Success to Builder Experience (BX) to recognize that people building with technology now include more than traditional coders. The team identifies three audiences: developers; AI builders, such as prompt engineers and agent creators; and automators using no-code or low-code tools. It says it will invest in resources, content, and community programs for this broader group, while keeping its existing developer documentation, forum, YouTube channel, and LinkedIn presence. The article frames the change as a response to AI expanding who can build, citing industry survey and GitHub figures; these figures are presented as context for the rebrand, not as a comparison of specific tools.

### Source excerpt

The builder revolution is here. Learn why Okta's team is now Builder Advocacy and what it means for developers, AI builders, and automators.

## How Verifiable Digital Credentials Are Reshaping Trust Architecture

DevFeed: [How Verifiable Digital Credentials Are Reshaping Trust Architecture](<https://devfeed.tech/articles/how-verifiable-digital-credentials-are-reshaping-trust-architecture-133746.md>)

Original publisher: [Read original article](<https://developer.okta.com/blog/2026/06/29/verifiable-digital-credentials/>)

Author: Akanksha Bhasin

Published: 2026-06-29T00:00:00Z

Content type: article

Language: en

Sources: [Okta Developer](<https://devfeed.tech/sources/okta-developer.md>)

Topics: [trust](<https://devfeed.tech/topics/trust.md>), [digital wallet](<https://devfeed.tech/topics/digital-wallet.md>), [protocols](<https://devfeed.tech/topics/protocols.md>), [Digital Trust](<https://devfeed.tech/topics/digital-trust.md>), [Passkeys](<https://devfeed.tech/topics/passkeys.md>), [openid](<https://devfeed.tech/topics/openid.md>), [WebAuthn](<https://devfeed.tech/topics/webauthn.md>)

Tags: [api](<https://devfeed.tech/tags/api.md>), [architecture](<https://devfeed.tech/tags/architecture.md>), [browser](<https://devfeed.tech/tags/browser.md>), [browsers](<https://devfeed.tech/tags/browsers.md>), [credentials](<https://devfeed.tech/tags/credentials.md>), [cryptographic](<https://devfeed.tech/tags/cryptographic.md>), [data](<https://devfeed.tech/tags/data.md>), [data-collection](<https://devfeed.tech/tags/data-collection.md>), [digital-credentials](<https://devfeed.tech/tags/digital-credentials.md>), [digital-wallet](<https://devfeed.tech/tags/digital-wallet.md>), [disclosure](<https://devfeed.tech/tags/disclosure.md>), [identity](<https://devfeed.tech/tags/identity.md>), [jwt](<https://devfeed.tech/tags/jwt.md>), [mobile](<https://devfeed.tech/tags/mobile.md>), [sd](<https://devfeed.tech/tags/sd.md>), [security](<https://devfeed.tech/tags/security.md>), [trust](<https://devfeed.tech/tags/trust.md>), [vc](<https://devfeed.tech/tags/vc.md>)

### AI overview

Verifiable Digital Credentials let an application verify a specific claim from a wallet-held credential, reducing document handling and the personal data it needs to store. The article distinguishes authentication (establishing a session) from verification, which it recommends adding at higher-trust checkpoints such as age gates, license checks, and sensitive actions. It describes SD-JWT VC as suited to web and backend uses such as age, employment, and license verification, while mdoc serves government identity use cases with stricter interoperability expectations. OpenID4VP handles credential presentation; OpenID4VCI handles issuance; the W3C Digital Credentials API invokes wallets in supported browsers. A valid signature alone is insufficient: verifiers need trusted issuers, governance rules, and key-rotation handling. Since native browser API support is still rolling out, the article recommends redirect-based OpenID4VP as the baseline, with the API added where supported, and suggests starting with one bounded verification need and its minimum required claim.

### Source excerpt

Verifiable Digital Credentials are reshaping trust. Learn the Issuer-Holder-Verifier model, SD-JWT VC, mdoc, OpenID4VP, and how to build the verifier side.

## Long Story Short: I Found My Place Between Code and Community

DevFeed: [Long Story Short: I Found My Place Between Code and Community](<https://devfeed.tech/articles/long-story-short-i-found-my-place-between-code-and-community-133745.md>)

Original publisher: [Read original article](<https://developer.okta.com/blog/2026/06/24/aasawari-sahasrabuddhe-intro-blog/>)

Author: Aasawari Sahasrabuddhe

Published: 2026-06-24T00:00:00Z

Content type: opinion

Language: en

Sources: [Okta Developer](<https://devfeed.tech/sources/okta-developer.md>)

Topics: [developer-relations](<https://devfeed.tech/topics/developer-relations.md>), [okta](<https://devfeed.tech/topics/okta.md>), [coding-community](<https://devfeed.tech/topics/coding-community.md>), [CI/CD](<https://devfeed.tech/topics/cicd.md>)

Tags: [2](<https://devfeed.tech/tags/2.md>), [ai](<https://devfeed.tech/tags/ai.md>), [ai-systems](<https://devfeed.tech/tags/ai-systems.md>), [authentication](<https://devfeed.tech/tags/authentication.md>), [backend](<https://devfeed.tech/tags/backend.md>), [ci-cd](<https://devfeed.tech/tags/ci-cd.md>), [code](<https://devfeed.tech/tags/code.md>), [community](<https://devfeed.tech/tags/community.md>), [containers](<https://devfeed.tech/tags/containers.md>), [content](<https://devfeed.tech/tags/content.md>), [developer-advocate](<https://devfeed.tech/tags/developer-advocate.md>), [developer-relations](<https://devfeed.tech/tags/developer-relations.md>), [docker](<https://devfeed.tech/tags/docker.md>), [engineer](<https://devfeed.tech/tags/engineer.md>), [engineering](<https://devfeed.tech/tags/engineering.md>), [frameworks](<https://devfeed.tech/tags/frameworks.md>), [gitops](<https://devfeed.tech/tags/gitops.md>), [identity](<https://devfeed.tech/tags/identity.md>), [java](<https://devfeed.tech/tags/java.md>), [okta](<https://devfeed.tech/tags/okta.md>), [security](<https://devfeed.tech/tags/security.md>)

### AI overview

The author moved from backend engineering into developer relations to combine coding with education, public speaking, content, workshops, and community work. Their technical background includes Java, Quarkus, Spring Boot, containers, Kubernetes, Docker, CI/CD, and GitOps, alongside recognition as a MongoDB Champion. Now joining Okta, they are interested in how identity supports trust, access, and governance for AI systems, and look forward to learning Okta's products and connecting with the community.

### Source excerpt

From backend engineer to AI Builder Advocate at Okta -- how developer relations, identity security, and community brought me here.

[Next page](<https://devfeed.tech/sources/okta-developer.md?cursor=WyIyMDI2LTA2LTI0VDAwOjAwOjAwKzAwOjAwIiwgIjI3NWJkN2ZkLTc2NTctNDIxOS05ZmIxLTQxMzQ3NTI4MzdmNyJd>)