On This Page
|Change||Expected in Preview Orgs|
|Password Import Inline Hook in General Availability in Preview and Production||February 5, 2020|
|OAuth for Okta Enabled for User Consent Grant Operations||February 5, 2020|
|OAuth for Okta Enabled for Policy API||February 5, 2020|
|User Types API in General Availability in Preview||February 5, 2020|
|SAML Assertion Inline Hook Now Supports URI Formatting in Claims||February 5, 2020|
|Support Added in List Users API for Sort Parameters||February 5, 2020|
|Apps API Support for Custom SAML Attribute Statements||February 5, 2020|
|Rate Limits for OAuth 2.0 Endpoints in Production||n/a|
|Bugs Fixed in 2020.02.0||February 5, 2020|
The Password Import Inline Hook lets you interface with an external service to verify a user-supplied password when the user signs in to Okta for the first time. This supports scenarios in which users are migrated from an existing user store while allowing them to retain their passwords.
The User Types API is in General Availability (GA) in Preview.
Okta now supports URI claims with the SAML Assertion Inline Hook. When you need to replace or add a URI claim, you must encode the claim name within the command based on the JSON Pointer specification.
The List Users API now supports
sortOrder parameters on
The Apps API now supports specifying SAML attribute statements for SAML 2.0 apps.
Rate limiting has been modified for OAuth 2.0 endpoints in Production orgs so that requests that use an invalid client ID don't consume the rate limit. A System Log warning has also been introduced for high rate limit consumption by requests that use a valid client ID.
When using the SAML Assertion Inline Hook, if there was an optional attribute statement configured for the app and the attribute statement had no value specified, commands returned from SAML Inline Hook responses were not applied. (OKTA-263494)
The Update User Types API previously allowed the existing name of a User Type to be changed. (OKTA-241788)