Zum Inhalt springen

Okta Identity Engine Updates & Release Notes

3 Einträge aus 1 Quelle. Zuletzt aktualisiert:

Folge Okta Identity Engine, um die Release Notes in deinen Feed zu holen.

Angaben zum Datum

Datum aus dem Text des Eintrags.

Erstmals gesehen am .

Okta Identity Engine von Okta

Okta Identity Engine 2026.09.0: Android 14–17 und Cross App Access

In Okta Identity Engine 2026.09.0 unterstützen Device-Assurance-Richtlinien nun Android 14 bis 17, enhanced dynamic zones kennen neue IP-Service-Kategorien als eigene VPN-Kategorie, und Cross App Access (XAA) steht allen Kunden zur Absicherung des Zugriffs von KI-Agenten und Apps zur Verfügung.

Device assurance OS version update

The following OS versions are now supported in device assurance policies: Android 14, 15, 16, 17 (2026-08-01)

New IP service categories for enhanced dynamic zones

Several new IP service categories are now supported as an individual VPN service category in enhanced dynamic zones. See Supported IP categories.

Cross App Access support for AI agents and apps for all customers

Use XAA to secure access between custom SSO-agentic requesting apps and SSO resource apps. XAA enables customers to connect AI agents and apps to take action on behalf of a user, and removes the need for user consent at runtime. The XAA connection is managed by Okta admins, providing them with visibility and control over which actions an AI agent can take on behalf of a user across the supported OIDC and SAML SSO protocols.

  • For the agentic requesting app configuration, see Add AI agents manually, and select your SSO agentic app in User access > App used for access configuration.
  • For the XAA resource app configuration, see Configure resource server connectors. If you're configuring an OIN resource app, it must already have XAA enabled. …

Originalquelle(öffnet in neuem Tab)Problem melden

Datum unbekanntAngaben zum Datum

Kein Datum in der Quelle. Der Eintrag stammt aus dem ersten Abruf der Quelle, der Tag der Aufnahme sagt nichts über das Erscheinen.

Erstmals gesehen am .

Okta Identity Engine von Okta

Okta Identity Engine 2026.09.1: KI-Agenten per CIMD registrieren

Okta Identity Engine 2026.09.1 ermöglicht die Registrierung von KI-Agenten per CIMD mit einer URL statt einer statischen Client-ID, zeigt MCP-Server-Scopes in einem separaten Dialog an und weist in Okta Access Requests offene Manager-Aufgaben und -Fragen bei einem Managerwechsel automatisch dem neuen Manager zu.

CIMD for AI agents

You can now register AI agents with a CIMD so that they can identify themselves with a URL instead of a static client ID. See About Client ID Metadata Documents (CIMD).

UI update for MCP server scopes

Now when you add custom scopes to an MCP server, the list of scopes appears in a separate dialog. See Add an MCP server manually.

Automatic tasks and questions reassignment after a manager change

To prevent access requests from being blocked during organizational changes, Okta Access Requests now automatically reassigns pending manager tasks and manager questions to an employee's new manager whenever a manager change occurs. This automated reassignment ensures that approvals proceed without manual IT intervention or delays, even if the previous manager's account has already been deactivated. This is available for requests built with both request conditions and request types.

Requester timeline view …

Originalquelle(öffnet in neuem Tab)Problem melden

Datum unbekanntAngaben zum Datum

Kein Datum in der Quelle. Der Eintrag stammt aus dem ersten Abruf der Quelle, der Tag der Aufnahme sagt nichts über das Erscheinen.

Erstmals gesehen am .

Okta Identity Engine von Okta

Okta Identity Engine 2026.09.2: Eindeutige MCP-Namen, Sign-In Widget 7.49.1

Okta Identity Engine 2026.09.2 verlangt eindeutige Anzeigenamen für MCP-Server, wählt bei Okta FastPass in Authentifizierungsketten standardmäßig „Phishing resistant“ aus, bringt das Sign-In Widget 7.49.1, konfigurierbare Begründungen für Entscheidungen bei Access Requests sowie Provisioning für Kong AI.

Unique MCP server names

When you register an MCP server, it must now have a unique display name. 

Sign-In Widget, version 7.49.1

For details about this release, see Sign-In Widget Release Notes. For more information about the widget, see Okta Sign-In Widget.

Automatic phishing resistance for FastPass in authentication chains

When you include Okta FastPass in an authentication method chain, the Phishing resistant characteristic is now selected by default. 

Access Requests decision justification

Okta Identity Governance now supports configurable justification controls for access request decisions, providing requesters more transparency into their approvals and denials. Admins can configure the approval sequence or request type settings to include the decision justification field for approval tasks, allowing approvers the option to provide a rationale for their decision. All submitted justification text is captured on the request ticket and made available to the requester, providing insight into access decisions. See Request type settings.

Provisioning for Kong AI

Provisioning is now available for the Kong AI integration. See Integrate Kong AI with Okta.

Editable resource URL for MCP servers …

Originalquelle(öffnet in neuem Tab)Problem melden