Okta Corporate Blog

For decades, the System Authorization Access Request (SAAR) Form DD-2875 has been a common Department of War (DoW) rite of passage. Yet, as our operational environments shift toward cloud architectures, multi-domain operations, and aggressive timelines, the traditional DD-2875 process has become a clear liability. Its reliance on manual data entry, sequential paper or email-based approvals, and static documentation cannot scale to modern mission demands. Fortunately, change is underway.

Change history for every flow—no backup strategy required TL;DR: Okta Workflows introduces Early Access flow versioning, providing a native 30-day change history and one-click revert capabilities. This feature ensures accountability and reduces operational downtime by tracking who made edits, when they occurred, and what logic changed. Why flow versioning matters for Okta Workflows For organizations relying on automation to run mission-critical operations, execution reliability isn't optional.

Executive summary Okta’s dedicated waste management program centers on creating healthy, low-impact physical spaces that minimize landfill waste. This four-part blog series covers our strategy for decarbonizing our real estate footprint using green procurement and green lease standards, establishing global consistency in operational waste management, prioritizing healthy workspace design via LEED and WELL certifications, and mindfully engaging our employees in our program.

When you visit any website, it may store or retrieve information on your browser, mostly in the form of cookies. This information might be about you, your preferences or your device and is mostly used to make the site work as you expect it to. The information does not usually directly identify you, but it can give you a more personalized web experience. Because we respect your right to privacy, you can choose not to allow some types of cookies.

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.

TL;DR: Modern enterprise security requires deep integration between identity providers and SaaS applications. Buyers today prioritize interoperable providers that go beyond basic access control integrations to unlock business agility and threat defense. The Okta Integration Network (OIN) provides a vehicle for SaaS services to support two critical identity security capabilities: Express Configuration and Universal Logout.

AI agents have evolved from novelties into active participants in enterprise workflows. They now operate across systems, reading data, executing actions, and calling APIs on behalf of users. This evolution creates a new security hurdle for enterprises. Software and agents need to connect without relying on static API keys, scattered OAuth consent, or unmanaged integrations. Cross App Access (XAA) addresses this by bringing these connections under the enterprise identity layer.

When you visit any website, it may store or retrieve information on your browser, mostly in the form of cookies. This information might be about you, your preferences or your device and is mostly used to make the site work as you expect it to. The information does not usually directly identify you, but it can give you a more personalized web experience. Because we respect your right to privacy, you can choose not to allow some types of cookies.

Contributor: Houssem Eddine Bordjiba Executive Summary Since April 2026, a threat actor tracked as O-UNC-066 (also known as "Pink" by Palo Alto Networks Unit 42) has deployed a panel-controlled phishing kit targeting the passkey enrollment process for Microsoft 365 customers. Okta has observed the targeting of enterprise organizations across the food and beverage, technology, healthcare, automotive, construction, and aviation industries by this cluster of activity.

If you currently federate enterprise customers using Security Assertion Markup Language (SAML) and want to allow AI agents to access your API 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.