Zum Inhalt springen

Okta Classic Engine Updates & Release Notes

3 Einträge aus 1 Quelle. Zuletzt aktualisiert:

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

Angaben zum Datum

Datum aus der Quelle.

Erstmals gesehen am .

Okta Classic Engine von Okta

Okta Classic Engine 2026.09.2: Begründungsfelder und Kong-AI-Provisioning

Okta Classic Engine 2026.09.2 ermöglicht in Okta Identity Governance konfigurierbare Begründungsfelder für Entscheidungen bei Access Requests, stellt Provisioning für die Kong-AI-Integration bereit und behebt Fehler wie falsche ROLE_ASSIGNED_USER_ACTIVATION-Audit-Ereignisse, langsames Laden der User-Sources-Seite und inkonsistente Anzeige des Drittanbieter-Admin-Status im Admin-Role-Assignment-Report.

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.

Fixes

  • When an import job reconciled existing active admin users, Okta incorrectly logged false ROLE_ASSIGNED_USER_ACTIVATION audit events. This issue created misleading records when no role changes occurred. (OKTA-1274235)

  • The User Sources page loaded slowly if there was a large number of profile sources. (OKTA-1265698)

  • When generating the Out-of-the-Box Admin Role Assignment report, the third-party admin status appeared inconsistently for users with multiple admin roles assigned through group memberships. (OKTA-1278183) …

Originalquelle(öffnet in neuem Tab)Problem melden

Angaben zum Datum

Datum aus der Quelle.

Erstmals gesehen am .

Okta Classic Engine von Okta

Okta Classic Engine 2026.09.1: Manager-Aufgaben und Status-Timeline

Okta Classic Engine 2026.09.1 weist bei einem Managerwechsel offene Manager-Aufgaben und -Fragen in Access Requests automatisch dem neuen Manager zu, bietet Anfragenden eine Status-Timeline für ihre Aufgaben und behebt mehrere Fehler, darunter mehrfache user.mfa.factor.update-Ereignisse nach Okta-Verify-Updates auf iOS und ein fehlerhaftes Profil-Update aller Active-Directory-Benutzer beim Import eines einzelnen Service-Accounts.

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

Requesters can now view a detailed status timeline of their request's tasks directly from the Okta Access Request app. This enhanced visibility allows requesters to easily track the progress of their requests, see who has approved individual tasks, and identify remaining tasks, helping users stay informed throughout the approval process and reducing unnecessary status inquiries. The timeline is available for requests built with access request conditions.

Fixes

  • When users updated the Okta Verify app on iOS devices, the System Log recorded multiple user.mfa.factor.update events within a single day. (OKTA-1215063)

  • When an admin begin a user import for a single service account without an Okta user object, the profile sync process incorrectly updated all users in the Active Directory instance. (OKTA-1267422) …

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 Classic Engine von Okta

Okta Classic Engine 2026.09.0: Neue IP-Kategorien, JA4-Fingerprints, Agents

Okta Classic Engine 2026.09.0 unterstützt neue IP-Service-Kategorien als einzelne VPN-Service-Kategorie in Enhanced Dynamic Zones, erfasst JA4-TLS-Fingerprints über alle Syslog-Ereignistypen (noch nicht für Orgs mit Custom-Hosted Domains), zeigt den Fortschritt laufender Importe im Import-Monitoring-Dashboard in Echtzeit und bringt den Okta On-Prem MFA Agent 1.8.7 mit Sicherheitsverbesserungen sowie den Radius Agent 2.27 mit internen Verbesserungen und Fehlerbehebungen.

Version: 2026.09.0

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.

Okta On-Prem MFA agent version 1.8.7

This version includes security enhancements.

Radius Agent version 2.27

This version includes internal improvements and fixes.

JA4 TLS fingerprinting

Okta now captures JA4 TLS client fingerprints across Syslog event types (securityContext.tlsFingerprint.ja4 pr), instead of just a curated subset. This includes telephony events (for example, OTP/SMS delivery) along with sign-in, auth, and token events. This provides customers and Okta's security teams with fingerprint-level visibility to spot bot traffic, toll fraud, and other TLS-based attack patterns that IP/user-agent signals miss on their own.

This is not yet available for orgs on custom-hosted domains.

Enhanced import monitoring with real-time updates

You can now view real-time progress for imports from the Import Monitoring dashboard. This provides greater visibility into the current status of in-progress imports such as the number of data chunks currently being processed.

Copy email from-addresses to the default brand domain …

Originalquelle(öffnet in neuem Tab)Problem melden