On This Page
|Change||Expected in Preview Orgs|
|Email as a factor and supported optional enrollment is Generally Available in Preview||March 4, 2020|
|The Third-Party admin role is Generally Available in Preview||March 4, 2020|
|OAuth for Okta is Generally Available in Preview||March 4, 2020|
|Pagination is available for the List Authorization Servers operation||March 4, 2020|
|Sign-in attempt behavior evaulation is now logged when there is no client information||March 4, 2020|
|OAuth for Okta enabled for Schemas and Linked Objects APIs||March 4, 2020|
|Bugs fixed in 2020.03.0||March 4, 2020|
The Okta email factor for MFA is now Generally Available in Preview. When the email factor is enabled, end users receive a code in an email message to use when they sign in.
The email factor configuration also supports optional enrollment, which is now Generally Available for all orgs that already have the factor enabled as part of Early Access.
The Third-Party admin role is now Generally Available in Preview.
OAuth for Okta is now Generally Available in Preview. At this time, OAuth for Okta works only with the APIs listed in the Scopes & supported endpoints section. We are actively working towards supporting additional APIs. Our goal is to cover all Okta public API endpoints.
Pagination is now available for the List Authorization Servers operation.
Sign-in attempt behavior evaluation is logged in the
debugContext object of the
policy.evaluate.sign_on events, even when client information is missing for all behaviors.
The Schemas API and the Linked Objects API now have OAuth for Okta enabled. See Scopes & supported endpoints.
- Users could acquire logs before the Logs retention period using specific
- App admins were able to modify all profiles in the Profile Editor even when the admin was limited to only administer certain apps. (OKTA-267829)