Published , by The Key editors.
Okta Agent SSO reaches general availability
In short: Okta made Agent SSO generally available on 24 August 2026. It is built on Cross App Access and included in core Okta SSO. Agents can reach SaaS apps for a signed-in user through Okta, rather than storing a separate token for each app.
Okta announced general availability of Agent SSO on 24 August 2026. The release implements Cross App Access. Its central role is delegated access: the identity provider brokers an agent's access to an application for a user who has signed in. That is the capability to assess first when reading the announcement.
Okta states that Agent SSO is included in core Okta SSO. For existing customers, the inclusion removes a separate product cost barrier described in the current note. Our recommendation is to distinguish that inclusion from a broader claim about the cost of adoption. The announcement's inclusion statement should remain the basis for any pricing description here.
The access model gives agents a route to SaaS applications through Okta rather than storing a separate token for each application. We recommend starting an evaluation with a specific user, agent and destination application. Ask how that intended relationship maps to the delegated access model. This is a suggested review method, not a claim that every application is covered.
Agent SSO follows Okta for AI Agents, which became generally available on 29 April 2026. That earlier release included agent registration in Universal Directory and human owners. Registration and ownership provide a different point of comparison from access brokerage. Our recommendation is to keep those functions distinct in an assessment, even when both matter to the same deployment.
The release boundary also matters. Okta lists Agent Gateway and human involvement in the approval loop as coming after general availability. Approval for individual actions is therefore not part of this release. Buyers should not read delegated access as a statement that every proposed agent action receives a person's approval.
Our editorial recommendation is to write down whether the requirement concerns access to an application or approval of a particular action. Use that distinction when selecting a path through the key. Agent SSO is the lead product in the result for delegated access with Cross App Access. A requirement for approval belongs in a separate evaluation rather than being assumed from the SSO label.
For a practical review, compare the stated requirement with the documented release, not with later capabilities listed as forthcoming. Ask which parts rely on agent registration, which rely on a human owner and which rely on access brokerage. These are evaluation questions intended to expose unclear assumptions. They do not add capabilities to the announcement.
The most useful reading of this release is specific rather than expansive. Okta made a delegated access capability generally available and included it in core SSO. We recommend recording that fact alongside the explicit boundary around approvals. That keeps the assessment focused on what the release actually describes.
Sources: Okta Agent SSO press release; Okta for AI Agents general availability, read 2026-11-03