On This Page
|Change||Expected in Preview Orgs|
|Features API is Generally Available in Production||December 11, 2019|
|Token Inline Hook is Generally Available in Production||December 11, 2019|
|SAML Inline Hook is Generally Available in Production||December 11, 2019|
|Scope Object Properties Default Values||December 11, 2019|
|Okta-Hosted User Consent Dialog Change||December 11, 2019|
|OAuth for Okta Enabled for Clear User Sessions Endpoint||December 11, 2019|
|Bug Fixed in 2019.12.0||December 11, 2019|
The Features API allows operations to manage self-service Early Access features in Production and Preview orgs, as well as manage self-service Beta features in Preview orgs and view Beta features in Production orgs.
The Token Inline Hook enables you to integrate your own custom functionality into the process of minting OAuth 2.0 and OpenID Connect tokens.
The SAML Inline Hook enables you to customize SAML assertions returned by Okta. You can add attributes or modify existing attributes in outbound SAML assertions.
In Scope objects created using the Authorization Server API, the default values of the
description properties were updated to be more informative.
In OAuth 2.0 or OpenID Connect authentication flows, Okta-hosted user consent dialogs were updated to display neutral colors for some UI elements.
The Clear User Sessions endpoint now has OAuth for Okta enabled.
- In the Authorization Server API, supplying a
consentproperty was previously required when creating a Scope object in orgs that had the EA feature enabled. It is now required only when updating existing Scope objects. (OKTA-250368)