# Okta > Identity and access management company providing authentication, authorization, single sign-on, and identity security solutions. ## Articles ### [Supercharge Auth with Signals and the New Okta Angular SDK](https://yomu.fyi/post/supercharge-auth-with-signals-and-the-new-okta-angular-sdk.md) - Company: [Okta](https://yomu.fyi/company/okta.md) - Author: Alisa Duncan - Published: Aug 25, 2026 The updated Okta Angular SDK introduces fully standalone architecture, eliminating NgModules and wrapper functions in favor of standalone providers and functional guards. In an Angular v22 sample project, authentication is configured with the provideOktaAuth function without requiring a custom backend. Route security utilizes functional guards, while user and group data fetch flows are handled using rxResource alongside signal inputs. To support dynamic environments without requiring rebuilds or redeployments, the setup implements runtime configuration loading via provideAppInitializer and OktaAuthConfigService. Security is further bolstered by binding access tokens to browser key pairs using Demonstrating Proof of Possession alongside OAuth 2.1 and OpenID Connect protocols. ### [Add Cross App Access to Your OIDC Requesting Application](https://yomu.fyi/post/add-cross-app-access-to-your-oidc-requesting-application.md) - Company: [Okta](https://yomu.fyi/company/okta.md) - Author: Sohail Pathan - Published: Aug 21, 2026 OpenID Connect federated applications connecting to third-party services can implement Cross App Access using the Identity Assertion Authorization Grant specification. When a user authenticates via the standard authorization code flow, the requesting application retains the issued refresh token. The application exchanges this refresh token at Okta's token endpoint via RFC 8693 token exchange to receive a short-lived Identity Assertion Authorization Grant JSON Web Token. Next, the application presents this assertion to the third-party resource authorization server using the RFC 7523 JWT bearer grant to obtain a final access token. Developers can configure an AI Agent and application integrations in Okta to validate the entire end-to-end request flow against test endpoints on xaa.dev. ### [I Found My Coordinates: Code, Community, and Okta](https://yomu.fyi/post/i-found-my-coordinates-code-community-and-okta.md) - Company: [Okta](https://yomu.fyi/company/okta.md) - Author: Vanshika Pandey - Published: Aug 20, 2026 A career progression through community leadership and software engineering led to a new role at Okta. Starting as a campus ambassador and Google Developer Student Clubs lead in India, the author organized hackathons, workshops, and meetups to foster peer learning. To effectively advocate for developers, an internship as a Developer Advocate at Zuplo prompted hands-on engineering experience as a Software Development Engineer at JPMorgan. After mentoring over 10,000 students and growing a technical community to over 600,000 members, the author joined Okta as a Senior Builder Advocate. In this role, advocacy extends beyond traditional coders to support AI builders, low-code creators, and developers utilizing identity and access management tools. ### [Build a Flask App with Okta for Secure OIDC Login and Authorized API Calls](https://yomu.fyi/post/build-a-flask-app-with-okta-for-secure-oidc-login-and-authorized-api-c.md) - Company: [Okta](https://yomu.fyi/company/okta.md) - Author: Akanksha Bhasin - Published: Jul 28, 2026 Flask web applications require dedicated mechanisms to authenticate users securely and authorize access to downstream services. Developers can address this by integrating Okta as an OpenID Connect identity provider using the Authlib library. Authlib registers Okta as a remote provider and automates the Authorization Code flow using Proof Key for Code Exchange with SHA-256 code challenge verification. After logging in through Okta and completing the callback route, the Flask web application uses the acquired OAuth 2.0 access token to query a protected backend resource server. This architecture ensures that user credentials remain managed by Okta while client requests to backend API endpoints carry valid, scoped authorization tokens. ### [Enable Your SAML Requesting App for Cross App Access](https://yomu.fyi/post/enable-your-saml-requesting-app-for-cross-app-access.md) - Company: [Okta](https://yomu.fyi/company/okta.md) - Author: Alisa Duncan - Published: Jul 17, 2026 Cross App Access allows enterprise applications federated with Security Assertion Markup Language to interact with third-party resource APIs without migrating to OpenID Connect. The flow adapts the Identity Assertion Authorization Grant specification to SAML by adding three token exchange steps following the standard single sign-on handshake. First, the application exchanges the validated SAML assertion for an OAuth refresh token using Okta's token endpoint and a private key JSON Web Token. The application then uses the refresh token to request a short-lived Identity Assertion Authorization Grant token from Okta. Finally, the application presents the Identity Assertion Authorization Grant token to the third-party authorization server to obtain an OAuth access token. ### [Introducing Okta Journeys: A Better Way for Developers to Learn Identity](https://yomu.fyi/post/introducing-okta-journeys-a-better-way-for-developers-to-learn-identit.md) - Company: [Okta](https://yomu.fyi/company/okta.md) - Author: Dan Maharry - Published: Jul 7, 2026 Okta has introduced Journeys, a task-oriented documentation format designed to streamline how developers learn and implement identity management. Rather than requiring engineers to manually assemble information across disparate guides, articles, and API references, each Journey provides an end-to-end curriculum for a specific project. Content is organized into three distinct phases: foundational knowledge in Learn, architectural decision-making in Plan, and curated implementation steps in Build. The initial release includes six Journeys aimed at Okta Customer Identity builders who are implementing authentication, registration, branding, and user management. Future additions will address AI agent governance, integrations for the Okta Integration Network, and migrations from the Classic Engine to the Okta Identity Engine.