|Change||Expected in Preview Orgs||Rollout to Production Orgs Expected to Start|
|New Device Notification Emails are Generally Available||September 5, 2018||September 10, 2018|
|Email Rate Limiting||September 5, 2018||September 10, 2018|
|New sendEmail Parameter for User Deletion and Deactivation||September 5, 2018||October 15, 2018|
|Support for JWTs Signed with Private Keys||September 5, 2018||September 10, 2018|
|System Log Event for Rate Limit Override Expiration||September 5, 2018||September 10, 2018|
|Required Properties in App User Schema||September 5, 2018||September 10, 2018|
|Previously Released Early Access Features 2018.36 Update||Available now||Available now|
When enabled, end users will receive a new device notification email when signing in to Okta from a new or unrecognized device. This feature is now generally available to all orgs. For more information about email notifications, refer to the New or Unknown Device Notification Emails section on this page.
Okta is introducing new rate limits for emails that are sent to users. This will help with service protection.
User deletion and deactivation requests now have an optional
sendEmail parameter. For more information see the documentation for those endpoints:
A System Log event will be generated exactly two days before a temporary API rate limit override is set to expire. The limit's expiration is set by customer support based on a window agreed upon when the override was requested. Once a limit has expired, it will no longer take effect and the customer will be subject to the default limit for that API endpoint.
API calls to modify an app user schema can no longer change the nullability (
required field) of a property if that property is shown as required in the default predefined schema for that app.
The following features have already been released as Early Access. To enable them, contact Support.
|Early Access Features Available Now|
|Custom URL Domains|
|Custom Okta-hosted Sign-In Page|
|Custom Error Page|
|Linked Objects API|
|Token Management API|
|User Consent for OAuth 2.0 and OpenID Connect Flows|