Okta API Products Release Notes

These release notes list customer-visible changes to API Products by release number. We release first to preview orgs and then production orgs.

Dates for preview release are the earliest possible release date. Always check your org to verify the release for your org.

To verify the current release for an org, check the footer of the administrator UI. If necessary, click the Admin button to navigate to your administrator UI.
Release Number in Footer

Note: Changes to Okta unrelated to API Products are published in the Okta Release Notes (opens new window).

2021.01.1

Change Expected in Preview Orgs
Bugs fixed in 2021.01.1 January 13, 2021

Bugs fixed in 2021.01.1

  • Active Directory (AD) bulk imports and RealTimeSync (RTS) failed when the Microsoft AD user profile contained tokenGroups, tokenGroupsGlobalAndUniversal, or tokenGroupsNoGCAcceptable attributes. (OKTA-354900)

  • In the SmartSheet provisioning profile, admins were unable to change the Group Priority setting to Combine values across groups for the smartsheet.userPermissions variable. The error message “Not allowed to modify property userPermissions from the base schema” was returned. (OKTA-325187)

2021.01.0

Change Expected in Preview Orgs
Group object source property is now GA in Production January 7, 2021
New Apps API endpoints in Early Access (EA) January 7, 2021
Developers can now use SWA for testing SCIM app integrations January 7, 2021
The Subscriptions API is now available in Self-Service Early Access (EA) January 7, 2021
New phone rate limits January 7, 2021
WebAuthn feature validation updates with Trusted Origins API January 7, 2021
Bug fixed in 2021.01.0 January 7, 2021

Group object source property is now GA in Production

For Groups API requests that return a Group or a list of Groups, the Group object type APP_GROUP includes a source property that provides the ID of the source application for the returned Group. This property is now GA in Production. See Group attributes.

New Apps API endpoints in Early Access (EA)

The Apps API now includes additional Early Access endpoints and objects for provisioning connections and features:

These updates improve the ability of administrators to configure application logos and provisioning details, previously available only through the Admin Console.

Note: Currently, only the Okta Org2Org application supports Application Provisioning Connection and Application Features operations.

Developers can now use SWA for testing SCIM app integrations

ISVs and developers who want to create and submit a SCIM-only app integration to the OIN can now use SWA as the sign-in method for SCIM app testing.

The Subscriptions API is now available in Self-Service Early Access (EA)

The Subscriptions API is now available in Self-Service EA. The Subscriptions API provides operations to manage email subscription settings for Okta administrator notifications.

New phone rate limits

Users who attempt Voice and SMS enrollment can now be rate limited. Voice and SMS enrollment rate-limit events are now logged in the System Log.

See System Log events for rate limits.

WebAuthn feature validation updates with Trusted Origins API

The WebAuthn feature now supports trusted cross-origin and cross-Relying Party Identifier (RP ID) validation when using the Trusted Origins API. Trusted Origins are configured in the Okta Trusted Origins framework either through the Admin Console or using the API. These Trusted Origins, configured with the CORS scope, now support orgs using WebAuthn for sign-in pages hosted at Trusted Origins distinct from the org's Okta URL (that is, different from the org's Okta or custom domain URL).

Bug fixed in 2021.01.0

Non-CORS requests to the OAuth 2.0 /introspect and /revoke endpoints failed when the Okta session cookie was present. (OKTA-356288)

2020.12.2

Change Expected in Preview Orgs
Manage email subscription settings using the Subscriptions API December 22, 2020
Bugs Fixed in 2020.12.2 December 22, 2020

Manage email subscription settings using the Subscriptions API

The /subscriptions API is now available in Self-Service EA. The Subscriptions API provides operations to manage email subscription settings for Okta administrator notifications.

Bugs fixed in 2020.12.2

  • Clients making GET requests to /api/v1/users/{usernameprefix} received an error if the user's short name (usernameprefix) ended with .jpg, .png, .js, .css, or a similar file extension, even when a user matching that short name existed. (OKTA-322140)
  • When an MFA policy was created without specifying the consent format, subsequent GET and UPDATE requests resulted in an error. (OKTA-339250)
  • The /users/${userId}/groups endpoint incorrectly returned a 500 Internal Server Error if the last page contained no elements. (OKTA-358328)

2020.12.1

Change Expected in Preview Orgs
Bugs Fixed in 2020.12.1 December 17, 2020

Bugs fixed in 2020.12.1

  • The Update User API incorrectly allowed the Credentials object of an ACTIVE user to be updated to Password Hook. (OKTA-350956)
  • The illegal_post_logout_redirect_uri error message, which was enhanced to help clients using the app client configuration wizard, incorrectly appeared for OIN clients. (OKTA-343082)

2020.12.0

Change Expected in Preview Orgs
Inclusive language and terminology December 9, 2020
New OAuth Administrator Roles API scopes December 9, 2020
New endpoint added to DynamicScale Rate Limits December 9, 2020
Account linking for SAML IdPs is now GA in Production December 9, 2020
One Time Use Refresh Token is now in Early Access (EA) December 9, 2020
Enhancements to Apps API for Idp Initiated Logins December 9, 2020
Enhancements to Apps API for SAML Apps December 9, 2020
Groups API extended search is now GA in Preview December 9, 2020

Inclusive language and terminology

Okta is focused on the adoption of inclusive language and communication. Some long-standing industry terminology and expressions have been updated in this release. More updates will be made in future releases.

In this release, the documentation for Custom Groups Claims has been updated with inclusive terminology. The term "whitelist" has been replaced with "allow list":

Existing custom claims that use the groupwhitelist Profile property don't need to change.

New OAuth Administrator Roles API scopes

The Administer Roles API now supports OAuth scopes okta.roles.manage and okta.roles.read. These scopes allow applications to read and manage (create, update, and delete) administrator roles in your Okta organization.

New endpoint added to DynamicScale rate limits

The DynamicScale add-on service now includes the following additional authentication endpoint: /login/login.html.

Account linking for SAML IdPs is now GA in Production

Admins can now enable or disable automatic account linking between SAML Identity Providers and Okta using the Identity Provider API. They can also restrict account linking based on whether the end user is a member of any specified groups.

One Time Use Refresh Token is now in Early Access (EA)

One Time Use Refresh Token, also called Refresh Token Rotation, is now in Early Access. Refresh Token Rotation helps a public client to securely rotate refresh tokens after each use. A new refresh token is returned each time the client makes a request to exchange a refresh token for a new access token. See Refresh Token Rotation.

Enhancements to Apps API for Idp Initiated Logins

The Apps API can now configure the Idp Initiated Login behavior, which is also available in the Admin Console. Note: The Idp Initiated Login is limited to OpenID Connect clients.

Enhancements to Apps API for SAML Apps

The Apps API can now configure the SLO URL behavior for SAML apps, which is also available in the Admin Console.

Groups API extended search is now GA in Preview

The Groups API support for extended search is now Generally Available (GA) in Preview.

2020.11.1

Change Expected in Preview Orgs
Bugs Fixed in 2020.11.1 November 11, 2020

Bugs fixed in 2020.11.1

  • Import of users with a bcrypt-hashed password succeeded even if the workFactor property was missing or misnamed. This prevented imported users from signing in. (OKTA-330587)
  • During user import, some POST requests to the /users endpoint incorrectly triggered Inline Hooks, resulting in higher latency. (OKTA-335769)

2020.11.0

Change Expected in Preview Orgs
Inclusive language and terminology November 4, 2020
System Log API adds additional filter expressions November 4, 2020
Zones API includes usage property November 4, 2020
Client-based rate limiting is now GA in Production (See entry)
User Consent for OAuth 2.0 and OpenID Connect flows is rolling out to GA in Production (See entry)
Account linking for SAML IdPs is now GA in Preview November 4, 2020
Group object source property is now GA in Preview November 4, 2020
MyAccount API is now in Early Access (EA) November 4, 2020
Bug Fixed in 2020.11.0 November 4, 2020

Inclusive language and terminology

Okta is focused on the adoption of inclusive language and communication. Some long-standing industry terminology and expressions have been updated in this release. More updates will be made in future releases.

The descriptive information returned on both the invalid redirect URI and invalid logout URI error pages has been updated to remove the term "whitelisted".

System Log API adds additional filter expressions

The System Log API /logs endpoint can now use the SCIM filter expression operators: ew (ends with), ne (not equal), and not (not function).

Zones API includes usage property

To help you manage zones in your organization, the Early Access Zones API now includes the usage attribute. There are two types of zones: Policy Network Zones and Block List Network Zones.

Client-based rate limiting is now GA in Production

Client-based rate limiting for the /authorize endpoint is now available in production orgs. It provides granular isolation between requests made to the /authorize endpoint by using a combination of the Client ID, user's IP address, and Okta device identifier. This isolates rogue OAuth clients and bad actors, ensuring valid users and applications don't run into rate limit violations.

This feature will be available to orgs in Okta Production cells on November 9, 2020.

A consent represents a user's explicit permission to allow an application to access resources protected by scopes. As part of an OAuth 2.0 or OpenID Connect authentication flow, you can prompt the user with a page to approve your app's access to specified resources. See the consent property for scopes.

This feature will be gradually made available to orgs in Okta Production cells beginning on November 11, 2020.

Account linking for SAML IdPs is now GA in Preview

Admins can now enable or disable automatic account linking between SAML Identity Providers and Okta using the Identity Provider API. They can also restrict account linking based on whether the end user is a member of any specified groups.

Group object source property is now GA in Preview

For API requests that return a Group or a list of Groups, the Group object includes a source property that provides the ID of the source application for the returned Group. This property is now GA in all Preview orgs. See Group attributes.

MyAccount API is now in Early Access (EA)

The MyAccount API enables non-administrator end users to fetch their Okta user profiles. To enable this EA feature, contact Support (opens new window).

Bug fixed in 2020.11.0

When the expiresAt property value of the Authentication transaction object was returned with an /authn response that also included the sessionToken parameter (not stateToken), the value incorrectly indicated a 3-minute lifetime. (OKTA-319907)

2020.10.2

Change Expected in Preview Orgs
Bug fixed in 2020.10.2 October 21, 2020

Bug fixed in 2020.10.2

When accessing the /authorize endpoint with a scope parameter requiring consent, users not assigned to the application received a consent prompt rather than an error message. (OKTA-335476)

2020.10.1

Change Expected in Preview Orgs
Bug fixed in 2020.10.1 October 14, 2020

Bug fixed in 2020.10.1

Requests that were missing access tokens resulted in an HTTP 400 error code instead of a 401. (OKTA-280102)

2020.10.0

Change Expected in Preview Orgs
Troubleshooting assistance for app redirect URI October 7, 2020
API Access Management enables scope as a claim October 7, 2020
Rate limit changes October 7, 2020
Client-based rate limiting October 7, 2020
Groups API enhancements in EA October 7, 2020

Troubleshooting assistance for app redirect URI

When an app redirect URI is either missing or incorrectly configured, Okta returns an HTTP 400 error. Now, the error description provides troubleshooting assistance to debug the expected redirect URI.

API Access Management enables scope as a claim

You can now name a claim scope in API Access Management custom authorization servers. Also, you can now use the EL expression access.scope in custom claims to return an array of granted scope strings.

Rate limit changes

Rate limits for paid developer orgs and for one-app orgs have been updated. See the Rate Limits page.

Client-based rate limiting

Client-based rate limiting for the /authorize endpoint is now available in Preview. It provides granular isolation between requests made to the /authorize endpoint by using a combination of the Client ID, user's IP address, and Okta device identifier. This isolates rogue OAuth clients and bad actors, ensuring valid users and applications don't run into rate limit violations.

Groups API enhancements in EA

The Groups API now supports extended search. Also, source application is now returned in Group objects.

2020.09.4

Change Expected in Preview Orgs
Bugs fixed in 2020.09.4 September 30, 2020

Bugs fixed in 2020.09.4

  • When an OAuth service client called the /authorize endpoint, the returned error description was inaccurate. (OKTA-252750)

  • If a user was assigned to two groups that have identical roles, then a call to the /users/${userId}/roles endpoint to list the administrator roles assigned to the user failed with an HTTP 400 error. (OKTA-325187)

  • The okta.apps.* scope wasn't applied to the /apps/${applicationId}/credentials/keys endpoint. (OKTA-331828)

2020.09.3

Change Expected in Preview Orgs
Bug fixed in 2020.09.3 September 24, 2020

Bug fixed in 2020.09.3

If a user was converted to use an external Federated IdP instead of Okta, any subsequent attempt to convert the user with a call to the /users/${userId}/lifecycle/reset_password endpoint returned an HTTP 501 error instead of an HTTP 400 error. (OKTA-323343)

2020.09.2

Change Expected in Preview Orgs
Bug fixed in 2020.09.2 September 16, 2020

Bug fixed in 2020.09.2

  • Requests to the /token, /revoke, and /introspect endpoints that had invalid client credentials would return an HTTP 400 error instead of the HTTP 401 error required by the OAuth 2.0 spec (opens new window). (OKTA-306444)

2020.09.1

Change Expected in Preview Orgs
Bugs fixed in 2020.09.1 September 10, 2020

Bugs fixed in 2020.09.1

  • When attempting to reset a user's password using the lifecycle/reset_password endpoint, admins received an HTTP 500 error code rather than a valid error message if the user's email address was invalid. (OKTA-307089)
  • If a Groups claim returned more than 100 groups, then tokens couldn't be minted, which generated an HTTP 500 error code instead of an HTTP 400 error code. (OKTA-321988)
  • If an Identity Provider returned an error response during authentication, the /introspect endpoint returned an HTTP 500 error code. (OKTA-324419)
  • When a geographical network zone that included Okta routers was added to an IP blacklist zone, all requests to the org were blocked. (OKTA-326955)

2020.08.2

Change Expected in Preview Orgs
Bugs fixed in 2020.08.2 August 19, 2020

Bugs fixed in 2020.08.2

  • In orgs with Factor Sequencing enabled, customers always had password as one of the factor types in the ID token's amr claim, regardless of which factor was actually used. (OKTA-318437)
  • For some orgs with both Passwordless Authentication and Improved New Device Behavior Detection enabled, Okta treated all authentication attempts as though they came from new devices. (OKTA-320675)

2020.08.0

Change Expected in Preview Orgs
Apple as an Identity Provider is now GA in Production August 5, 2020
OAuth 2.0 authorization code length has been increased August 5, 2020
Bugs fixed in 2020.08.0 August 5, 2020

Apple as an Identity Provider is now GA in Production

Apple as an Identity Provider is now Generally Available in Production. Apple as an IdP allows users to sign in to your app using their Apple ID. See Apple as an Identity Provider.

OAuth 2.0 authorization code length has been increased

To better align with security best practices (opens new window), the length of OAuth 2.0 authorization codes is now 256 bits of entropy (43 characters).

Bugs fixed in 2020.08.0

  • The GET /api/v1/users/{userid}/idps and POST /api/v1/idps/{idpId}/users/{userId} endpoints weren't OAuth enabled. (OKTA-303902)

  • Non-CORS requests to the OAuth 2.0 /token endpoint failed when the Okta session cookie was present. (OKTA-312816)

2020.07.2

Change Expected in Preview Orgs
Bug fixed in 2020.07.2 July 29, 2020

Bug fixed in 2020.07.2

  • When using the Apps API, exceeding the character limit for OIDC application redirect URIs resulted in an HTTP 500 error instead of an HTTP 400 error. (OKTA-297164)

2020.07.0

Change Expected in Preview Orgs
Apple as an Identity Provider is now GA in Preview July 9, 2020
YubiKey OTP Token operations added July 9, 2020
Support for creating OIN OIDC Apps via the Dynamic Client Registration API July 9, 2020
API support for multiple ACS URLs July 9, 2020
Bugs fixed in 2020.07.0 July 9, 2020

Apple as an Identity Provider is now GA in Preview

Apple as an Identity Provider is now Generally Available in Preview. Apple as an IdP allows users to sign in to your app using their Apple ID. See Apple as an Identity Provider.

YubiKey OTP Token operations added

Using the Factors API, requests for single YubiKey OTP Tokens and uploading a seed for a YubiKey OTP are now supported. Other API operations for YubiKey OTP Tokens are now documented in the Factors API.

Support for creating OIN OIDC Apps using the Dynamic Client Registration API

Creating OIN OIDC Apps using the Dynamic Client Registration API is now supported.

API support for multiple ACS URLs

When creating a custom SAML app using the Apps API, you can now pass two optional parameters (allowMultipleAcsEndpoints and acsEndpoints) to configure up to 100 Assertion Consumer Service (ACS) URLs.

Bugs fixed in 2020.07.0

2020.06.2

Change Expected in Preview Orgs
Bug fixed in 2020.06.2 June 17, 2020

Bug fixed in 2020.06.2

After a user was demastered from Active Directory, calls to the /users endpoint did not reflect that change for up to 24 hours. (OKTA-294377)

2020.06.1

Change Expected in Preview Orgs
Bug fixed in 2020.06.1 June 10, 2020

Bug fixed in 2020.06.1

For deleted or inactive instances, or instances that don't support CVD, calls to the /mappings endpoint incorrectly returned HTTP 500 errors. (OKTA-287888)

2020.06.0

Change Expected in Preview Orgs
Password Import Event eligible for use in Event Hook June 3, 2020
OAuth public metadata endpoint caching June 3, 2020
Issuer identifier in tokens when using Custom URL Domain June 2, 2020
Improved new device behavior detection June 3, 2020
Dynamic authentication context for SAML apps June 2, 2020
New JWKS key length validation June 3, 2020

Password Import Event eligible for use in Event Hook

The user.import.password event provides information on the outcome of the import of an individual user's password during the Password Import flow. This event is eligible for use in an Event Hook, enabling you to trigger removal of a password from your existing user store when import to Okta is confirmed as successful.

OAuth public metadata endpoint caching

HTTP no-cache headers are no longer sent in responses returned by the following OAuth public metadata endpoints:

  • /.well-known/openid-configuration
  • /.well-known/oauth-authorization-server
  • /oauth2/{authorizationServerId}/.well-known/openid-configuration
  • /oauth2/{authorizationServerId}/.well-known/oauth-authorization-server

Issuer identifier in tokens when using Custom URL Domain

When the Custom URL Domain feature is enabled and apps are configured to use CUSTOM_URL as the issuer_mode, tokens minted during an SP-initiated flow now use the request hostname in the value of the issuer identifier (iss) claim, while those minted during an IdP-initiated flow use the custom URL. This change currently only applies to new Preview orgs.

Improved new device behavior detection

When this feature is enabled, stronger signals are used for the detection of new devices. Devices with web browsers that don't store cookies are treated as new, and trusted applications must send a unique identifier for each device as a device token.

Dynamic authentication context for SAML apps

You can configure a custom attribute statement for SAML assertions to send user authentication context to SAML apps during the app authentication process. Apps can use this information to limit access to certain app-specific behaviors and calculate the risk profile for the signed-in user.

New JWKS key length validation

New client JSON Web Key Sets are now validated and rejected if the key length is less than 2048 bits.

2020.05.2

Change Expected in Preview Orgs
Bug fixed in 2020.05.2 May 20, 2020

Bug fixed in 2020.05.2

When listing AD and LDAP group targets for the Group admin role assigned to a user or to a group, the logo URL in the _links section of the response was incorrect. (OKTA-297070)

2020.05.1

Change Expected in Preview Orgs
Bugs fixed in 2020.05.1 May 13, 2020

Bugs fixed in 2020.05.1

  • Exceeding the rate limit on the /token endpoint resulted in an HTTP 400 error instead of an HTTP 429 error. (OKTA-289508)
  • The IdP /metadata.xml endpoint was not OAuth enabled. (OKTA-294739)
  • Simultaneous DELETE calls to the /users/${id} endpoint could result in HTTP 500 errors. (OKTA-223918)

2020.05.0

Change Expected in Preview Orgs
Logging of successful password import May 6, 2020
Rate limit headers no longer returned on cached static endpoints May 6, 2020
OAuth for Okta enabled for Trusted Origins, Sessions, and Custom Templates APIs May 6, 2020
Updated behavior for logging of invalid use by OAuth 2.0 Client May 6, 2020
Bugs fixed in 2020.05.0 May 6, 2020

Logging of successful password import

A System Log Event is now generated with details about the success or failure of the password import attempt when a user with an imported password has successfully signed in to Okta.

Rate limit headers no longer returned on cached static endpoints

Rate limits do not apply to these OAuth public metadata endpoints, so rate limit headers will no longer be returned:

  • /oauth2/v1/keys
  • /.well-known/openid-configuration
  • /.well-known/oauth-authorization-server
  • /oauth2/{authorizationServerId}/v1/keys
  • /oauth2/{authorizationServerId}/.well-known/openid-configuration
  • /oauth2/{authorizationServerId}/.well-known/oauth-authorization-server

OAuth for Okta enabled for Trusted Origins, Sessions, and Custom Templates APIs

OAuth for Okta is now enabled for the Trusted Origins API, the Sessions API, and the Custom Templates API. See Scopes & supported endpoints.

Updated behavior for logging of invalid use by OAuth 2.0 Client

The previously announced logging behavior has been updated. Invalid client_secret warnings are now triggered by 5 invalid attempts (consecutive or not) within a 24 hour period.

Bugs fixed in 2020.05.0

  • When signing in a federated user using the /oauth/v1/authorize endpoint with consent enabled and the prompt parameter set to login, the Sign-In Widget failed with an error. (OKTA-290760)

2020.04.2

Change Expected in Preview Orgs
Bugs fixed in 2020.04.2 April 29, 2020

Bugs fixed in 2020.04.2

  • Service clients weren't able to update users. (OKTA-288246)
  • Returned User Type objects erroneously contained a ref object. (OKTA-287651)

2020.04.1

Change Expected in Preview Orgs
Bug fixed in 2020.04.1 April 15, 2020

Bug fixed in 2020.04.1

  • When calling the /oauth2/default/v1/authorize or /oauth2/${authServerId}/v1/authorize endpoints with the prompt parameter set to login and the idp parameter set to a SAML IdP, the end user wasn't forced to authenticate. (OKTA-288118)

2020.04.0

Change Expected in Preview Orgs
OAuth for Okta GA in Production April 8, 2020
User Types API GA in Production April 8, 2020
CORS headers in more API responses April 8, 2020
Bugs fixed in 2020.04.0 April 8, 2020

OAuth for Okta GA in Production

OAuth for Okta is now Generally Available in Production.

User Types API GA in Production

The User Types API is Generally Available in Production.

CORS headers in more API responses

Okta will now return CORS headers for requests made with OAuth 2.0 Bearer tokens, even if an endpoint isn't CORS-enabled and even if the originating URL isn't configured as a Trusted Origin.

Bugs fixed in 2020.04.0

  • New SAML apps would have an active SAML assertion Inline Hook assigned to them automatically. (OKTA-262777)
  • Attempts to update the user schema with invalid properties could return HTTP 500 errors. (OKTA-281498)
  • The errorSummary for error E0000074 was malformed. (OKTA-273711)

2020.03.2

Change Expected in Preview Orgs
Bugs fixed in 2020.03.2 March 18, 2020

Bugs fixed in 2020.03.2

  • In some cases, an OAuth 2.0 /authorize request would incorrectly redirect if the client App had an App Sign-On Policy configured. (OKTA-269116)

  • The _links attribute for groups sent by Okta in the request body for a SAML Inline Hook was incorrect. (OKTA-269553)

  • Responses from OpenID Connect and OAuth 2.0 public metadata endpoints incorrectly omitted the return of CORS headers if the calling URL wasn't in the list of trusted origins defined for the org. (OKTA-283549)

  • When a Workflow was called, all headers that weren't white listed had text prepended in the response, which broke redirects. (OKTA-282294)

  • In some cases, the end user wasn't correctly prompted for consent during an OAuth 2.0 /authorize request. (OKTA-270039)

2020.03.1

Change Expected in Preview Orgs
Bug fixed in 2020.03.1 March 11, 2020

Bug fixed in 2020.03.1

  • The Update Identity Provider operation allowed changing the protocol property of an Identity Provider object, which resulted in errors. (OKTA-277221)

2020.03.0

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

Email as a factor and supported optional enrollment is Generally Available in Preview

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 Generally Available in Preview

The Third-Party admin role (opens new window) is now Generally Available in Preview.

OAuth for Okta is 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 available for the List Authorization Servers operation

Pagination is now available for the List Authorization Servers operation.

Sign-in attempt behavior evaluation is now logged when there is no client information

Sign-in attempt behavior evaluation is logged in the debugContext object of the user.session.start and policy.evaluate.sign_on events, even when client information is missing for all behaviors.

OAuth for Okta enabled for Schemas and Linked Objects APIs

The Schemas API and the Linked Objects API now have OAuth for Okta enabled. See Scopes & supported endpoints.

Bugs fixed in 2020.03.0

  • Users could acquire logs before the Logs retention period using specific after parameters. (OKTA-277912)
  • 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)

2020.02.2

Change Expected in Preview Orgs
Bugs fixed in 2020.02.2 February 26, 2020

Bugs fixed in 2020.02.2

  • When the Security Question option wasn't enabled in the password policy, requests to the /reset_password endpoint would return a 403 error when the sendEmail query parameter was set to false. (OKTA-272392)
  • Some cross-origin requests to the /users/me endpoint didn't return CORS headers if the user had an invalid session. (OKTA-260550)

2020.02.1

Change Expected in Preview Orgs
Bugs Fixed in 2020.02.1 February 19, 2020

Bugs Fixed in 2020.02.1

  • When an admin's last role was revoked using the Roles API, it would sometimes not trigger a System Log event. (OKTA-276093)
  • In certain situations the /keys endpoint would incorrectly return that the current key was expired and needed to be rolled over when the rollover hadn't occurred yet. (OKTA-227062)
  • Expired AD users received different authentication errors depending on whether the Passwordless Policy was enabled or disabled. (OKTA-268306)

2020.02.0

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

Password Import Inline Hook in General Availability in Preview and Production

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.

User Consent Grant Operations now have OAuth for Okta enabled.

OAuth for Okta Enabled for Policy API

The Policy API now has OAuth for Okta enabled.

User Types API in General Availability in Preview

The User Types API is in General Availability (GA) in Preview.

SAML Assertion Inline Hook Now Supports URI Formatting in Claims

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 (opens new window) specification.

Support Added in List Users API for Sort Parameters

The List Users API now supports sortBy and sortOrder parameters on search queries.

Apps API Support for Custom SAML Attribute Statements

The Apps API now supports specifying SAML attribute statements for SAML 2.0 apps.

Rate Limits for OAuth 2.0 Endpoints in Production

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.

Bugs Fixed in 2020.02.0

  • 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)

2020.01.2

Change Expected in Preview Orgs
Bug Fixed in 2020.01.2 January 29, 2019

Bug Fixed in 2020.01.2

  • Passing an incorrect userId to the List User Roles API would not result in an error. (OKTA-243094)

2020.01.0

Change Expected in Preview Orgs
Rate limit warnings for all API customers January 8, 2020
Events API endpoint rate limit added January 8, 2020
System Log Events for user import January 8, 2020

Rate limit warnings for all API customers

All Customer Identity orgs will now see an admin console banner and receive an email notification when their org approaches its rate limit. Previously this was only available for One App and Enterprise orgs.

Events API endpoint rate limit added

The /events API endpoint now has its own rate limit bucket for Workforce orgs. See the Rate Limits page for more information.

System Log Events for user import

System Log events have been added for the start and end of each phase of the user import process. See the Event Types catalog for more information.

2019.12.1

Change Expected in Preview Orgs
Bug Fixed in 2019.12.1 December 18, 2019

Bug Fixed in 2019.12.1

2019.12.0

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

Features API is Generally Available in Production

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.

Token Inline Hook is Generally Available in Production

The Token Inline Hook enables you to integrate your own custom functionality into the process of minting OAuth 2.0 and OpenID Connect tokens.

SAML Inline Hook is Generally Available in Production

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.

Scope Object Properties Default Values

In Scope objects created using the Authorization Server API, the default values of the displayName and 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.

OAuth for Okta Enabled for Clear User Sessions Endpoint

The Clear User Sessions endpoint now has OAuth for Okta enabled.

Bug Fixed in 2019.12.0

  • In the Authorization Server API, supplying a consent property 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)

2019.11.3

Change Expected in Preview Orgs
Bugs Fixed in 2019.11.3 December 4, 2019

Bugs Fixed in 2019.11.3

  • POST calls to the /api/v1/apps endpoint couldn't be used with OAuth for Okta. (OKTA-259867)

  • In some situations, ID tokens returned from Okta didn't contain the idp claim. (OKTA-253962)

2019.11.2

Change Expected in Preview Orgs
Bug Fixed in 2019.11.2 November 20, 2019

Bug Fixed in 2019.11.2

Multifactor (MFA) Enrollment Policy objects returned by Okta included an unused property, enroll.profiles. (OKTA-260160)

2019.11.1

Change Expected in Preview Orgs
Bug Fixed in 2019.11.1 November 13, 2019

Bug Fixed in 2019.11.1

An incorrect status was returned in some cases when an admin checked another user's session information using the Sessions API. (OKTA-245793)

2019.11.0

Change Expected in Preview Orgs
Web Authentication as a factor is Generally Available in Production November 6, 2019
Features API is Generally Available in Preview November 6, 2019
SAML Inline Hook is Generally Available in Preview November 6, 2019
Token Inline Hook is Generally Available in Preview November 6, 2019
OAuth for Okta is Early Access in Preview November 6, 2019
Concurrent requests to the same app now return exception November 6, 2019
Rate Limits for /oauth2 endpoints November 6, 2019
Bug Fixed in 2019.11.0 November 6, 2019

Web Authentication as a factor is Generally Available in Production

Admins can enable Web Authentication as a factor (WebAuthn) as defined by WebAuthn standards. WebAuthn supports both security key authentication such as YubiKey devices and platform authenticators such as Windows Hello.

Features API is Generally Available in Preview

The Features API provides operations to manage self-service Early Access features in your Production and Preview orgs and self-service Beta features in your Preview org.

SAML Inline Hook is Generally Available in Preview

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.

Token Inline Hook is Generally Available in Preview

The Token Inline Hook enables you to integrate your own custom functionality into the process of minting OAuth 2.0 and OpenID Connect tokens.

OAuth for Okta is Early Access in Preview

With OAuth for Okta, you are able to interact with Okta APIs using scoped OAuth 2.0 access tokens. Each access token enables the bearer to perform specific actions on specific Okta endpoints, with that ability controlled by which scopes the access token contains. For more details, see our OAuth for Okta guide.

Concurrent requests to the same app now return exception

Concurrent PUT requests sent to the same app instance now return an ApiException rather than a 500 HTTP server error.

Rate Limits for /oauth2 endpoints

Rate limiting (opens new window) has been modified for /oauth2 endpoints so that requests that use an invalid client ID don't consume rate limit. Additionally, a System Log warning has been introduced to provide notification of high rate limit consumption by requests that use a valid client ID.

Bug Fixed in 2019.11.0

When the Token Inline Hook feature was enabled and the claim couldn't be evaluated, the OAuth 2.0 token endpoint returned a 403 HTTP status code rather than 400. (OKTA-258981)

2019.10.2

Change Expected in Preview Orgs
User Types Error Message Change October 31, 2019
Bugs Fixed in 2019.10.2 October 31, 2019

User Types Error Message Change

Error messages returned by the User Types API have changed. Omitting display name or variable name when attempting to create a User Type, or specifying a variable name that is already in use, results in a more specific error message being returned.

Bugs Fixed in 2019.10.2

  • A SameSite=None attribute sent by Okta caused a bug in cross-site handling of cookies in Chrome on iOS 12.* or earlier. (OKTA-254174)
  • In the Features API, when using mode=force to enable a feature and its dependencies, email notifications were not sent to admins for Beta dependencies that were enabled. (OKTA-249644)
  • The length of EL expressions that you could specify for OAuth 2.0 claim values was previously limited to a shorter length but has now been increased to 1024 characters. (OKTA-237675)

2019.10.1

Change Expected in Preview Orgs
Maximum characters increased for the UserAgent string October 16, 2019

Maximum characters increased for the UserAgent string

The maximum length of the client.userAgent.rawUserAgent property value was increased from 200 to 500 characters. See UserAgent Object (opens new window) in the /logs API reference content for more information on this property.

2019.10.0

Change Expected in Preview Orgs
Event Hooks API is Generally Available October 9, 2019
User Types API in Early Access October 9, 2019
Tokens transform events no longer available October 9, 2019
Cookies updated to preserve cross-functionality October 9, 2019
App Condition available for Enroll Policy October 9, 2019
Bugs Fixed in 2019.10.0 October 9, 2019

Event Hooks API is Generally Available

The Event Hooks API is Generally Available (GA) in Production.

User Types API in Early Access

The User Types API is in Early Access (EA) in both Preview and Production.

Tokens transform events no longer available

Tokens transform System Log events will no longer fire for SAML and Token Inline Hooks. They have been replaced by Inline Hook events.

Cookies updated to preserve cross-functionality

To preserve cross-site functionality, Okta now adds the SameSite=None attribute to all relevant cookies when the client browser is Firefox 69 or above. Previously this was enabled only for Chrome 76 and above.

App Condition available for Enroll Policy

App Condition is now available for the Enroll Policy.

Bugs Fixed in 2019.10.0

  • WebAuthn Factors could not be verified using the Factors API. (OKTA-228239)
  • During OAuth 2 and OIDC sign-in flows, the Okta Sign-In Widget incorrectly rendered pre-populated usernames, substituting + with a space. (OKTA-235187)

2019.09.4

Change Expected in Preview Orgs
Scope Naming Restriction October 2, 2019

Scope Naming Restriction

OAuth Scopes are not allowed to start with the okta. prefix. See the Note under Scope properties for more information.

2019.09.3

Change Expected in Preview Orgs
Bug Fixed in 2019.09.3 September 25, 2019

Bug Fixed in 2019.09.3

  • After a user successfully scanned the QR code and completed the MFA enrollment process, the factorResult parameter was missing from the response. (OKTA-244102)

2019.09.2

Change Expected in Preview Orgs
Bugs Fixed in 2019.09.2 September 18, 2019

Bugs Fixed in 2019.09.2

  • When users signed in using IdP Discovery or a Default IdP, any outgoing Hooks related to that sign-in event contained an incorrect request URL value. (OKTA-243190)
  • GET requests to the /users/me endpoint would return hidden standard attributes. (OKTA-243864)

2019.09.0

Change Expected in Preview Orgs
Features API is Early Access EA in Preview and Production September 4, 2019
Mappings API is now Generally Available (GA) in Production September 4, 2019
Error Object in SAML Assertion Inline Hook September 4, 2019
Rate Limits for Authorization Server Public Metadata September 4, 2019
Bugs Fixed in 2019.09.0 September 4, 2019

Features API is Early Access (EA) in Preview and Production

The Features API provides operations to manage self-service features in your Production and Preview orgs and Beta features in your Preview org.

Mappings API is now Generally Available (GA) in Production

The Okta Mappings API provides operations to manage the mapping of properties between an Okta User's and an App User's Profile Properties using Expression Language. This feature is now GA in Production.

Error Object in SAML Assertion Inline Hook

For the SAML Assertion Inline Hook, if an external service returns an error object, Okta now denies the SAML request and redirects the end user to an error page that displays the text string sent in error.errorSummary.

Rate Limits for Authorization Server Public Metadata

The public metadata endpoints for Authorization Servers are now each assigned separate rate limits, which are not shared with other endpoints.

Bugs Fixed in 2019.09.0

  • Responses from the GET /groups/rules API included deleted groups in the assignUserToGroups.groupIds property. (OKTA-242994)

  • Calls to the /users/${userid}/lifecycle/deactivate endpoint could time out when deactivating a user with an extraordinarily high number of app assignments. (OKTA-228031)

2019.08.3

Change Expected in Preview Orgs
Bugs Fixed in 2019.08.3 August 29, 2019

Bugs Fixed in 2019.08.3

  • The Update Inline Hook call wasn't replacing the whole object. (OKTA-229337)

  • IP addresses identified as malicious by Okta ThreatInsight were missing from Events API ("security.threat.detected") event messages. See the Event Types catalog for more information on this event message. (OKTA-242795)

2019.08.2

Change Expected in Preview Orgs
Bug Fixed in 2019.08.2 August 21, 2019

Bug Fixed in 2019.08.2

Paginated responses from the List Users with Search API were limited to a total of 50,000 results, and following the next link after that limit yielded an error. (OKTA-220619)

2019.08.1

Change Expected in Preview Orgs
Bug Fixed in 2019.08.1 August 14, 2019

Bug Fixed in 2019.08.1

Some users were not able to access the Group Rules API, despite having proper permissions. (OKTA-240021)

2019.08.0

Change Expected in Preview Orgs
Added Support for TOTP Factor August 7, 2019
Cookies updated to preserve cross-site functionality August 7, 2019
Inline Hooks is now GA in Preview August 7, 2019
LinkedIn API V2 is now supported August 7, 2019
Mappings API is now GA in Preview August 7, 2019
Missing type property now returns a 400 error code August 7, 2019
Bug Fixed in 2019.08.0 August 7, 2019

Added Support for TOTP Factor

Okta now supports a custom MFA factor based on the Time-based One-time Password (TOTP) algorithm. For more information, see Custom HOTP Factor.

Cookies updated to preserve cross-site functionality

To preserve cross-site functionality in light of upcoming updates to Chrome (opens new window), Okta has added the SameSite=None attribute to all relevant cookies.

Inline Hooks is now GA in Preview

Inline Hooks enable you to integrate your own custom functionality into Okta process flows. The framework to support them is now Generally Available (GA) in Preview.

LinkedIn API V2 is now supported

Okta now supports LinkedIn API V2. Creation of LinkedIn Identity Providers has been re-enabled in all Production orgs.

Mappings API is now GA in Preview

The Okta Mappings API provides operations to manage the mapping of properties between an Okta User's and an App User's Profile Properties using Expression Language. This feature is now GA in Preview.

Missing type property now returns a 400 error code

If you create an IP network zone without a type property for an IP field, PUT or POST requests made to the Zone API now return a 400 error code.

Bug Fixed in 2019.08.0

In the Update User API, when the secondEmail attribute in a user's profile was updated with an empty value (instead of null), the user was incorrectly prompted for secondEmail. (OKTA-240382)

2019.07.2

Change Expected in Preview Orgs
Deleting App Groups July 31, 2019
Bug Fixed in 2019.07.2 July 31, 2019

Deleting App Groups

The DELETE /groups/${groupId} endpoint now supports deleting app groups, in addition to Okta groups. Note, however, that groups configured for group push cannot be deleted.

Bug Fixed in 2019.07.2

  • When API Access Management Consent was enabled, the factor lifetime configured in the App Sign On Rule was ignored and the "Do not challenge me on this device for XXX" prompt didn't appear to the end user when signing in to an OpenID application. (OKTA-2233290)

2019.07.0

Change Expected in Preview Orgs
Email Factor is now GA in Production July 10, 2019
LinkedIn IdP creation re-enabled in Preview July 10, 2019
Email Customization disabled for free orgs July 10, 2019

Email Factor is now GA in Production

The Email Factor is now Generally Available (GA) in all Production orgs.

LinkedIn IdP creation re-enabled in Preview

Creation of LinkedIn Identity Providers has been re-enabled in all Preview orgs.

Email Customization disabled for free orgs

To curtail phishing, free editions of Okta are no longer able to create and send customized email templates. For feature information, see Email and SMS Options (opens new window).

2019.06.4

Change Expected in Preview Orgs
Token expiration window increased to five years July 3, 2019
Bug Fixed in 2019.06.4 July 3, 2019

Token expiration window increased to five years

The refresh token expiration window has increased to a maximum of five years in custom authorization servers.

Bug Fixed in 2019.06.4

  • The SystemLog V1 event type security.password_spray.detected has been deprecated. For threat related information, see security.threat.detected events. (OKTA-233958)

2019.06.3

Change Expected in Preview Orgs
Token Inline Hook Can Modify Sub-Objects and Array Elements June 26, 2019
Bugs Fixed in 2019.06.3 June 26, 2019

Token Inline Hook Can Modify Sub-Objects and Array Elements

The Token Inline Hook now lets you modify particular sub-objects or array elements within objects contained in claims, without needing to update the rest of the object.

Bugs Fixed in 2019.06.3

  • When a customer used a Token Inline Hook and returned an error object to Okta, Okta failed to pass the error to the token requester. (OKTA-231397)

  • The issuer claim inside JWT tokens was erroneously changing to all lowercase causing JWT verification failure when the application was case-sensitive. (OKTA-235710)

  • When a customer called the POST /idps/credentials/keys endpoint and supplied an x5t#S256 parameter to specify the SHA-256 thumbprint of the certificate that they were adding, Okta failed to validate the thumbprint.

2019.06.0

Change Expected in Preview Orgs
Email Factor is now GA in Preview June 5, 2019
Users can be removed from Profile Masters June 5, 2019

Email Factor is now GA in Preview

The Email Factor is now Generally Available (GA) in all Preview orgs.

Users can be removed from Profile Masters

Users can now be unassigned from Apps that serve as their Profile Masters.

2019.05.3

Change Expected in Preview Orgs
Token Inline Hook Can Modify or Remove Existing Claims (Early Access) May 29, 2019
Bugs Fixed in 2019.05.3 May 29, 2019

Token Inline Hook Can Modify or Remove Existing Claims (Early Access)

The Token Inline Hook now supports changing or removing existing claims in tokens minted by the Okta Custom Authorization Server.

Bugs Fixed in 2019.05.3

  • Responses from the GET /groups/rules API failed to include a link to the next page of results in cases where there was more than one page. (OKTA-221434)

  • Calls to the /authorize endpoint during the Authorization Code with PKCE flow would fail if an idp parameter was supplied with the call (in Preview orgs only). (OKTA-229808)

2019.05.2

Change Expected in Preview Orgs
Bug Fixed in 2019.05.2 May 22, 2019

Bug Fixed in 2019.05.2

  • The response ID of the User Schema API wasn't consistent with the actual server details. When a request was sent to GET/URL/api/v1/meta/schemas/user/default from a preview org, the response ID always contained a production org URL. (OKTA-218937)

2019.05.1

Change Expected in Preview Orgs
Bugs Fixed in 2019.05.1 May 15, 2019

Bugs Fixed in 2019.05.1

  • When trusted apps overrode the device token, device fingerprints were lost. This caused unexpected behavior for new sign-on notification emails and device-based behavior detection. (OKTA-226646)
  • When a Group admin (who manages more than 1 user group) used the API to fetch users with pagination, the request failed to create a link for the next page of users. (OKTA-222660)

2019.05.0

Change Expected in Preview Orgs
The Registration Inline Hook is in Early Access (EA) May 8, 2019
Bugs Fixed in 2019.05.0 May 8, 2019

The Registration Inline Hook is in Early Access (EA)

The Registration Inline Hook allows you to integrate your own custom logic into Okta's Self-Service Registration flow.

Bugs Fixed in 2019.05.0

  • Assigning an admin role directly to a user failed if that user was part of a group with the same admin role assignment. (OKTA-223035)
  • The List Users with Search API returned outdated user data. (OKTA-215187)

2019.04.2

Change Expected in Preview Orgs
Hashed Password Imports with SHA-512 Algorithm May 1, 2019
Bugs Fixed in 2019.04.2 May 1, 2019

Hashed Password Imports with SHA-512 Algorithm

You can use the SHA-512 hash type when importing passwords.

Bugs Fixed in 2019.04.2

  • Concurrent requests to modify the same app instance would result in an HTTP 500 error. (OKTA-205283)
  • Responses from the /oauth2/${authServerId}/.well-known/oauth-authorization-server and /oauth2/${authServerId}/.well-known/openid-configuration endpoints for Custom Authorization Servers would append a query parameter (client_id) to the value returned for the jwks_uri property. Inclusion of the query parameter was misleading because you cannot use the query parameter when calling the JWKS URI. (OKTA-217289)

2019.04.1

Change Expected in Preview Orgs
The Event Hooks Feature is Now Available in EA April 17, 2019
Bug Fixed in 2019.04.1 April 17, 2019

The Event Hooks Feature is Now Available in EA

Event hooks enable you to use events within your Okta org to trigger process flows within your own software systems.

Bug Fixed in 2019.04.1

The applicable rate limit wasn't updated when the URL for the factor verification endpoint was changed. For more details, see our Rate Limits page. (OKTA-219067)

2019.04.0

Change Expected in Preview Orgs
IdP Extensible Matching Rules are now GA in Preview April 10, 2019
The SAML Inline Hook is in EA April 10, 2019
Rate Limits Updated April 10, 2019
The Sign-In Widget Version for the Custom Login Page has been Updated April 10, 2019
Bug Fixed in 2019.04.0 April 10, 2019

IdP Extensible Matching Rules are now GA in Preview

IdP extensible matching rules allow you to define a regular expression pattern to filter untrusted IdP usernames. For details, see our IdPs page.

The SAML Inline Hook is in EA

The SAML Inline Hook enables you to customize SAML assertions returned by Okta. For details, see our SAML Inline Hook page.

Rate Limits Updated

Okta's API rate limits have been updated:

  • OAuth 2 rate limits were updated and clarified for all orgs.
  • The limit for the api/v1/apps endpoint was updated for Enterprise orgs. For details, see our Rate Limits page.

The Sign-In Widget Version for the Custom Login Page has been Updated

Custom Sign-in Pages can now use Sign-In Widget version 2.18. When you select the "latest" option, you automatically use 2.18. For more information, see our Sign-In Widget page.

Bug Fixed in 2019.04.0

IdPs did not match the user with the USERNAME_OR_EMAIL property when IDP_EXTENSIBLE_MATCHING_RULES was enabled. For details, see our IdPs page. (OKTA-218007)

2019.03.3

Change Expected in Preview Orgs
Bugs Fixed in 2019.03.3 March 26, 2019

Bugs Fixed in 2019.03.3

2019.03.2

Change Expected in Preview Orgs
PKCE for Browser Clients, CORS Headers for OAuth 2 Token Endpoint March 20, 2019
Bugs Fixed in 2019.03.2 March 20, 2019

PKCE for Browser Clients, CORS Headers for OAuth 2 Token Endpoint

Okta now supports Proof Key for Code Exchange (PKCE) for browser clients and returns CORS headers on the OAuth 2.0 Token endpoints.

Bugs Fixed in 2019.03.2

  • Under some circumstances, users in a locked out state would receive success responses from the SMS recovery API. (OKTA-207288)
  • In some instances, users who were not Okta-mastered would have inaccurate passwordChanged values in API responses. (OKTA-210233)
  • SAML applications created through the API would not save the value for the HonorForceAuthn property. (OKTA-209083)
  • For SAML applications, the attributeStatements object would not update if a null value was passed as part of a PUT operation. (OKTA-209767)

2019.03.1

Note: Okta has changed our release model and version numbering. For more information, see here: https://support.okta.com/help/s/article/New-Okta-Release-Model (opens new window)

Change Expected in Preview Orgs
Bug Fixed in 2019.03.1 March 13, 2019
Previously Released Early Access Features 2019.03.1 Update Available Now

Bug Fixed in 2019.03.1

  • The Hypertext Application Language links for the inlineHooks API response objects referred to an invalid URL. (OKTA-1211982)

Previously Released Early Access Features 2019.03.1 Update

The following features have already been released as Early Access. To enable them, contact Support (opens new window).

Early Access Features Available Now
Custom URL Domains
Custom Okta-hosted Sign-In Page
Custom Error Page
User Consent for OAuth 2.0 and OpenID Connect Flows

2019.03.0

Note: Okta has changed our release model and version numbering. For more information, see: https://support.okta.com/help/s/article/New-Okta-Release-Model (opens new window)

Change Expected in Preview Orgs
Password Import Supports SHA-1 and MD5 March 6, 2019
Enable Role Assignment to Every Member of a Group March 6, 2019
New Rate Limits for /users/me March 6, 2019
Generic OIDC IdP is now GA in Preview March 6, 2019
User Search is now GA in Production March 6, 2019
The Import Inline Hook is in EA March 6, 2019
Previously Released Early Access Features 2019.03.0 Update Available Now

Password Import Supports SHA-1 and MD5

The Create/Update User API now supports importing users with SHA-1 and MD5 credentials. For more information, see our Users page.

Enable Role Assignment to Every Member of a Group

Super and Org Admins can now assign and unassign roles to every user in a group using the APIs. For more information, see our Roles page.

New Rate Limits for /users/me

The rate limits for the /users/me endpoint have been updated. For more information, see our Rate Limits page.

Generic OIDC IdP is now GA in Preview

Generic OpenID Connect allows users to sign in to an Okta org using their credentials from their existing account at an OIDC Identity Provider. A generic OIDC IdP can be a third-party IdP that supports OIDC, such as Salesforce or Yahoo or your own custom IdP. You can also configure federation between Okta orgs using OIDC as a replacement for SAML. For more information, see Federate Okta with OpenID Connect.

User Search is now GA in Production

Extended search capabilities for the /users endpoint is now Generally Available. For more information, see our Users page.

The Import Inline Hook is in EA

The Import Inline Hook enables you to add custom logic to the process of importing new users into Okta from an app.

Previously Released Early Access Features 2019.03.0 Update

The following features have already been released as Early Access. To enable them, contact Support (opens new window).

Early Access Features Available Now
Custom URL Domains
Custom Okta-hosted Sign-In Page
Custom Error Page
User Consent for OAuth 2.0 and OpenID Connect Flows

2019.02.0

Note: Okta has changed our release model and version numbering. For more information, see here: https://support.okta.com/help/s/article/New-Okta-Release-Model (opens new window)

Change Expected in Preview Orgs Rollout to Production Orgs Expected to Start
Imported Hashed User Passwords Generally Available February 6, 2019 March 11, 2019
Inline Hooks February 6, 2019 February 19, 2019
Token Inline Hook February 6, 2019 February 19, 2019
Signature and Digest Algorithms for Template WS-FED Apps February 6, 2019 February 19, 2019
Google Integration Updated February 6, 2019 February 19, 2019
High Capacity Rate Limits February 6, 2019 February 19, 2019
Creation of LinkedIn IdPs Temporarily Disabled February 14, 2019 February 19, 2019
Bug Fixed in 2019.02.0 February 6, 2018 February 19, 2019
Previously Released Early Access Features 2019.02.0 Update Available Now Available Now

Imported Hashed User Passwords Generally Available

Use of imported hashed passwords when creating or updating users in the Users API is now Generally Available (GA).

Inline Hooks

Inline Hooks enable you to integrate your own custom functionality into Okta process flows. The framework to support them is now in Early Access (EA/).

Token Inline Hook

The Token Inline Hook enables you to integrate your own custom functionality into the process of minting OAuth 2.0 and OpenID Connect tokens.

Signature and Digest Algorithms for Template WS-Fed Apps

Template WS-Fed applications can now choose between SHA1 and SHA256 options for their Signature and Digest Algorithms. In addition, all Template WS-Fed applications will have X.509 certs signed with SHA256.

Google Integration Updated

Okta's Google social login integration has been updated to account for the deprecation of the Google+ API. More information can be found in our Knowledge Base (opens new window).

High Capacity Rate Limits

A new High Capacity Rate Limit SKU is now available. The impacted endpoints and their rate limits can be found on our Rate Limits page.

Creation of LinkedIn IdPs Temporarily Disabled

We have disabled the creation of new LinkedIn identity providers until further notice due to the upcoming LinkedIn API V1 deprecation.

Bug Fixed in 2019.02.0

  • There was a typo in the error text returned when a property was set to a 4-byte UTF-8 character (such as an emoji) in a field that does not allow such characters.

Previously Released Early Access Features 2019.02.0 Update

The following features have already been released as Early Access. To enable them, contact Support (opens new window).

Early Access Features Available Now
Custom URL Domains
Custom Okta-hosted Sign-In Page
Custom Error Page
User Consent for OAuth 2.0 and OpenID Connect Flows

2019.01.2

Note: Okta has changed our release model and version numbering. For more information, see here: https://support.okta.com/help/s/article/New-Okta-Release-Model (opens new window)

Change Expected in Preview Orgs Rollout to Production Orgs Expected to Start
Bug Fixed in 2019.01.2 January 30, 2019 February 4, 2019
Previously Released Early Access Features 2019.01.2 Update Available Now Available Now

Bug Fixed in 2019.01.2

  • Admin roles that were granted, scoped, or revoked through the Roles API did not appear in the System Log.

  • Verifying an OTP using the Voice Call MFA factor failed when the user tried to verify with the OTP within 30 seconds after auto-activation of the Voice Call MFA factor.

Previously Released Early Access Features 2019.01.2 Update

The following features have already been released as Early Access. To enable them, contact Support (opens new window).

Early Access Features Available Now
Custom URL Domains
Custom Okta-hosted Sign-In Page
Custom Error Page
User Consent for OAuth 2.0 and OpenID Connect Flows

2019.01.0

Note: Okta has changed our release model and version numbering. Under the old system, this would have been release 2019.1. For more information, see here: https://support.okta.com/help/s/article/New-Okta-Release-Model (opens new window)

Change Expected in Preview Orgs Rollout to Production Orgs Expected to Start
Social Authentication Generally Available January 9, 2019 January 14, 2019
IdP Discovery Generally Available January 9, 2019 January 14, 2019
Relay State Format Now Configurable for SAML IdPs January 9, 2019 January 14, 2019
No Events API Access for New Orgs January 9, 2019 January 14, 2019
Updated Office 365 Legacy Rate Limit January 9, 2019 January 14, 2019
Bug Fixed in 2019.01.0 January 9, 2018 January 14, 2019
Previously Released Early Access Features 2019.01.0 Update Available Now Available Now

Social Authentication Generally Available

Social Authentication is now Generally Available (GA).

IdP Discovery Generally Available

IdP Discovery is now Generally Available (GA) as part of the Policy API.

Relay State Format Now Configurable for SAML IdPs

The Protocol Object now contains a Relay State object that allows an admin to configure the Relay State format on the SAML IdP.

No Events API Access for New Orgs

As part of the deprecation process, new orgs created from this release onwards will not have access to the Events API.

Updated Office 365 Legacy Rate Limit

The default legacy rate limit for the /app/office365/{key}/sso/wsfed/active endpoint has been lowered from 2000 to 1000.

Bug Fixed in 2019.01.0

  • Some orgs were unable to create the number of users that they were entitled to. (OKTA-203819)

Previously Released Early Access Features 2019.01.0 Update

The following features have already been released as Early Access. To enable them, contact Support (opens new window).

Early Access Features Available Now
Custom URL Domains
Custom Okta-hosted Sign-In Page
Custom Error Page
User Consent for OAuth 2.0 and OpenID Connect Flows

2018.12.2

Note: Okta has changed our release model and version numbering. Under the old system, this would have been release 2018.52. For more information, see here: https://support.okta.com/help/s/article/New-Okta-Release-Model (opens new window)

Change Expected in Preview Orgs Rollout to Production Orgs Expected to Start
Bugs Fixed in 2018.12.2 December 27, 2018 January 7, 2019
Previously Released Early Access Features 2018.12.2 Update Available Now Available Now

Bugs Fixed in 2018.12.2

  • An error would be returned if the /apps/${applicationId} endpoint was called to update an app that did not not have a configurable signOnMode property.

  • The Identity Providers API endpoints GET /idps/${idpId}/users, GET /idps/${idpId}/users/{userId}, and DELETE /idps/${idpId}/users/${userId} previously required the social authentication feature, even for users related to a non-social IdP. Additionally, non-Social IdPs were not included in the results returned by GET /users/${userId}/idps.

  • Instead of providing specific reasons for failure, Identity Providers operations failed with generic error_description values when the Social Auth provider required user attributes in the user's profile but the attributes were missing or invalid.

  • The /users/${userId}/factors/catalog endpoint returned email as a supported factor type even when Email Authentication was not enabled for the org in MFA settings.

Previously Released Early Access Features 2018.12.2 Update

The following features have already been released as Early Access. To enable them, contact Support (opens new window).

Early Access Features Available Now
Custom URL Domains
Custom Okta-hosted Sign-In Page
Custom Error Page
User Consent for OAuth 2.0 and OpenID Connect Flows

2018.12.1

Note: Okta has changed our release model and version numbering. Under the old system, this would have been release 2019.50. For more information, see here: https://support.okta.com/help/s/article/New-Okta-Release-Model (opens new window)

Change Expected in Preview Orgs Rollout to Production Orgs Expected to Start
Bug Fixed in 2018.12.1 December 12, 2018 December 17, 2018
Previously Released Early Access Features 2018.12.1 Update Available Now Available Now

Bug Fixed in 2018.12.1

  • Requests to the same Okta Org Authorization Server's /keys endpoint failed if the requests originated from different domains in the same browser. (OKTA-156155)

Previously Released Early Access Features 2018.12.1 Update

The following features have already been released as Early Access. To enable them, contact Support (opens new window).

Early Access Features Available Now
Custom URL Domains
Custom Okta-hosted Sign-In Page
Custom Error Page
User Consent for OAuth 2.0 and OpenID Connect Flows

2018.12.0

Note: Okta has changed our release model and version numbering. Under the old system, this would have been release 2019.49. For more information, see here: https://support.okta.com/help/s/article/New-Okta-Release-Model (opens new window)

Change Expected in Preview Orgs Rollout to Production Orgs Expected to Start
Bug Fixed in 2018.12.0 December 5, 2018 December 10, 2018
Previously Released Early Access Features 2018.12.0 Update Available Now Available Now

Bug Fixed in 2018.12.0

  • Queries to the /logs endpoint would return an HTTP 500 error if they contained encoded curly braces (%7Bor %7D).

Previously Released Early Access Features 2018.12.0 Update

The following features have already been released as Early Access. To enable them, contact Support (opens new window).

Early Access Features Available Now
Custom URL Domains
Custom Okta-hosted Sign-In Page
Custom Error Page
User Consent for OAuth 2.0 and OpenID Connect Flows

2018.48

Change Expected in Preview Orgs Rollout to Production Orgs Expected to Start
System Log API Returns Threat Insight Attribute November 28, 2018 December 3, 2018
Bugs Fixed in 2018.48 November 28, 2018 December 3, 2018
Previously Released Early Access Features 2018.48 Update Available Now Available Now

System Log API Returns Threat Insight Attribute

The debugContext object returned by the System Log API can now include an okta_threat_insight attribute to indicate that an event has been identified as a security risk.

Bugs Fixed in 2018.48

  • Some customers could access log data outside of their allowed retention range through the System Log API.

  • Responses from the /oauth2/${authServerId}/.well-known/oauth-authorization-server endpoint did not include supported OpenID Connect response types in the content of the response_types_supported property.

Previously Released Early Access Features 2018.48 Update

The following features have already been released as Early Access. To enable them, contact Support (opens new window).

Early Access Features Available Now
Custom URL Domains
Custom Okta-hosted Sign-In Page
Custom Error Page
Token Management API
User Consent for OAuth 2.0 and OpenID Connect Flows

2018.45

Change Expected in Preview Orgs Rollout to Production Orgs Expected to Start
Linked Objects API is Generally Available (GA) November 6, 2018 December 10, 2018
Bugs Fixed in 2018.45 November 6, 2018 November 12, 2018
Previously Released Early Access Features 2018.45 Update Available Now Available Now

Linked Objects API is Generally Available (GA)

The Linked Objects API is now available to all orgs.

Bugs Fixed in 2018.45

  • The set of roles allowed access to system log information by the Events API did not match the set of roles allowed access by the System Log API. (OKTA-194899)
  • When a user tried to sign in using the Okta Sign-in Widget, they would not be prompted to enroll an optional factor, despite multiOptionalFactorEnroll being set to true. (OKTA-195195)

Previously Released Early Access Features 2018.45 Update

The following features have already been released as Early Access. To enable them, contact Support (opens new window).

Early Access Features Available Now
Custom URL Domains
Custom Okta-hosted Sign-In Page
Custom Error Page
Token Management API
User Consent for OAuth 2.0 and OpenID Connect Flows

2018.44

Change Expected in Preview Orgs Rollout to Production Orgs Expected to Start
Bugs Fixed in 2018.44 October 31, 2018 November 5, 2018
Previously Released Early Access Features 2018.44 Update Available Now Available Now

Bugs Fixed in 2018.44

  • Temporary passwords returned by the /users/${userId}/lifecycle/expire_password endpoint sometimes included hard-to-distinguish characters.
  • Queries to the /logs endpoint with since and until values that were both earlier than the customer's data retention period would return an HTTP 500 error.

Previously Released Early Access Features 2018.44 Update

The following features have already been released as Early Access. To enable them, contact Support (opens new window).

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

2018.42

Change Expected in Preview Orgs Rollout to Production Orgs Expected to Start
Bugs Fixed in 2018.42 October 17, 2018 October 22, 2018
Previously Released Early Access Features 2018.42 Update Available Now Available Now

Bugs Fixed in 2018.42

  • The /clients endpoint dropped the filter parameter for any paginated results returned after the first page.
  • Messages that were sent to devices using the Factors API would sometimes return a 500 error if the message could not be sent.

Previously Released Early Access Features 2018.42 Update

The following features have already been released as Early Access. To enable them, contact Support (opens new window).

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

2018.41

Change Expected in Preview Orgs Rollout to Production Orgs Expected to Start
Rate Limit Notifications for One App and Enterprise October 10, 2018 October 15, 2018
OIDC Clients Can Initiate Logout with Expired Token October 10, 2018 October 15, 2018
Change to User Link Editing Permissions October 10, 2018 October 15, 2018
Bugs Fixed in 2018.41 October 10, 2018 October 15, 2018
Previously Released Early Access Features 2018.41 Update Available Now Available Now

Rate Limit Notifications for One App and Enterprise

When an org reaches its rate limit, the admin console will display a banner and the admin(s) will receive an email notification. These notifications will only appear on One App and Enterprise organizations.

OIDC Clients Can Initiate Logout with Expired Token

Client-initiated logout now succeeds even when the ID token is no longer valid.

Editing the link between users now requires edit permissions for all users involved.

Bugs Fixed in 2018.41

  • Queries to the /logs endpoint with values for since and until that did not specify the time to milliseconds would sometimes return events outside of the specified time range. (OKTA-191533)
  • Responses from the /events endpoint would sometimes omit milliseconds from the published field. (OKTA-192568)

Previously Released Early Access Features 2018.41 Update

The following features have already been released as Early Access. To enable them, contact Support (opens new window).

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

2018.40

Change Expected in Preview Orgs Rollout to Production Orgs Expected to Start
Bugs Fixed in 2018.40 October 3, 2018 October 8, 2018
Previously Released Early Access Features 2018.40 Update Available Now Available Now

Bugs Fixed in 2018.40

  • Responses from the /zones endpoint included a duplicate of the type field. (OKTA-188605)
  • The /idps/credentials/keys endpoint was requiring requests to include extra parameters. (OKTA-189780)

Previously Released Early Access Features 2018.40 Update

The following features have already been released as Early Access. To enable them, contact Support (opens new window).

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

2018.39

Change Expected in Preview Orgs Rollout to Production Orgs Expected to Start
Bugs Fixed in 2018.39 September 26, 2018 October 1, 2018
Previously Released Early Access Features 2018.39 Update Available Now Available Now

Bugs Fixed in 2018.39

  • Requests to the /authorize endpoint would incorrectly prioritize values from the URI query parameter, rather than the request JWT. For more information, see the documentation for that endpoint. (OKTA-187642)
  • When multiple attempts were simultaneously made to update a user's phone number for the SMS or Call Factor, an HTTP 500 error was sometimes returned. (OKTA-188112)
  • In some situations SHA-256 password imports would not work. SHA-256 password import now requires the salt to be base64-encoded.

Previously Released Early Access Features 2018.39 Update

The following features have already been released as Early Access. To enable them, contact Support (opens new window).

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

2018.38

Change Expected in Preview Orgs Rollout to Production Orgs Expected to Start
User Sessions Deleted after Password Reset September 19, 2018 October 15, 2018
Bugs Fixed in 2018.38 September 19, 2018 September 24, 2018
Previously Released Early Access Features 2018.38 Update Available Now Available Now

User Sessions Deleted after Password Reset

We now delete all sessions for a user after a successful password reset as part of the forgot password flow.

Bugs Fixed in 2018.38

  • An HTTP 500 error would occur if the JSON body sent to create a user contained a non-string value for the following user profile properties: firstName, lastName, email, login, mobilePhone, and secondEmail. Any non-string values for these properties will now be converted into strings after they are sent. (OKTA-170711)

Previously Released Early Access Features 2018.38 Update

The following features have already been released as Early Access. To enable them, contact Support (opens new window).

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

2018.36

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

New Device Notification Emails are Generally Available (GA)

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 (opens new window).

Email Rate Limiting

Okta is introducing new rate limits for emails that are sent to users. This will help with service protection.

New sendEmail Parameter for User Deletion and Deactivation

User deletion and deactivation requests now have an optional sendEmail parameter. For more information see the documentation for those endpoints:

Support for JWTs Signed with Private Keys

Requests to the /token and /authorize endpoints will now accept JWTs signed with a private key. For more information see the OIDC documentation for the token endpoint and the authorize endpoint.

System Log Event for Rate Limit Override Expiration

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.

Required Properties in App User Schema

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.

Previously Released Early Access Features 2018.36 Update

The following features have already been released as Early Access. To enable them, contact Support (opens new window).

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

2018.35

Change Expected in Preview Orgs Rollout to Production Orgs Expected to Start
Bugs Fixed in 2018.35 August 29, 2018 September 4, 2018
Previously Released Early Access Features 2018.35 Update Available now Available now

Bugs Fixed in 2018.35

  • Search queries to the /user endpoint with an invalid after parameter would return an HTTP 500 error. (OKTA-185186)

Previously Released Early Access Features 2018.35 Update

The following features have already been released as Early Access. To enable them, contact Support (opens new window).

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

2018.33

Change Expected in Preview Orgs Rollout to Production Orgs Expected to Start
Bugs Fixed in 2018.33 August 15, 2018 August 20, 2018
Previously Released Early Access Features 2018.33 Update Available now Available now

Bugs Fixed in 2018.33

  • If an SMS factor was used within 30 seconds of the factor being auto-activated, verification would fail. (OKTA-178568)
  • In some instances, Org administrators would not be allowed to create new users, despite having the proper permissions. Additionally, the system log erroneously showed successful user creation. (OKTA-169709)

Previously Released Early Access Features 2018.33 Update

The following features have already been released as Early Access. To enable them, contact Support (opens new window).

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

2018.32

Change Expected in Preview Orgs Rollout to Production Orgs Expected to Start
Interstitial Page Settings are Generally Available (GA) August 8, 2018 September 2018
New System Log Event Type for Denied Events August 8, 2018 August 13, 2018
Bugs Fixed in 2018.32 August 8, 2018 August 13, 2018
Previously Released Early Access Features 2018.32 Update Available now Available now

Interstitial Page Settings are Generally Available

You can now disable the Okta loading animation that appears during a login redirect to your application. For more information, see Manage the Okta interstitial page (opens new window).

New System Log Event Type for Denied Events

The System Log now reports when requests are denied due to a blacklist rule (such as a IP network zone or location rule). These events are logged with the event type security.request.blocked. (OKTA-178982)

Bugs Fixed in 2018.32

  • Fixed a bug that affected delegated authentication users: in rare cases, the user appeared to be active when locked out, or vice versa. (OKTA-180932)
  • The Apps API now returns an error if changing the Application's self-service assignment settings could result in an insecure state. (OKTA-182497)

Previously Released Early Access Features 2018.32 Update

The following features have already been released as Early Access. To enable them, contact Support (opens new window).

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

2018.31

Change Expected in Preview Orgs Rollout to Production Orgs Expected to Start
Bugs Fixed in 2018.31 August 1, 2018 August 6, 2018
Previously Released Early Access Features 2018.31 Update Available now Available now

Bugs Fixed in 2018.31

  • Fixed an issue in the OpenID Connect logout endpoint where performing logout with an expired session resulted in an error instead of following the post_logout_redirect_uri. (OKTA-180521)

  • Removed System Logs entries for granting refresh tokens in token requests with the refresh_token grant type (since this grant type simply returns the original refresh token). This fix applies to both custom Authorization Servers and the Okta Org Authorization Server. (OKTA-178335)

  • Fixed issues with the User-Consent Grant Management API: added missing value to issuer, removed issuerId, removed HAL links for issuer and revoke, and added hints for self GET and DELETE. (OKTA-175296)

  • Fixed a bug where SAML apps created using the API could not enable honorForceAuthn. (OKTA-166146)

  • Fixed an issue where login_hint was ignored when using OAuth consent with a custom Authorization Server. (OKTA-164836)

Previously Released Early Access Features 2018.31 Update

The following features have already been released as Early Access. To enable them, contact Support (opens new window).

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

2018.29

Change Expected in Preview Orgs Rollout to Production Orgs Expected to Start
Bugs Fixed in 2018.29 July 18, 2018 July 23, 2018
Previously Released Early Access Features 2018.29 Update Available now Available now

Bugs Fixed in 2018.29

  • Using the Zones API to modify an existing zone that is blacklisted removed the blacklisting and coverted it to a normal IP Zone. (OKTA-176610)
  • Using the Applications API to create an OAuth client caused an error if the credentials.oauthClient property was not provided, even though it is not required. (OKTA-179275)
  • The System Log CSV report did not contain a value for AuthenticationContext.issuer for the event type user.authentication.authenticate. (OKTA-147165)

Previously Released Early Access Features 2018.29 Update

The following features have already been released as Early Access. To enable them, contact Support (opens new window).

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

2018.28

Change Expected in Preview Orgs Rollout to Production Orgs Expected to Start
MFA Call Factor is Generally Available (GA) July 11, 2018 July 16, 2018
Bugs Fixed in 2018.28 July 11, 2018 July 16, 2018
Previously Released Early Access Features 2018.28 Update Available now Available now

MFA Call Factor is Generally Available (GA)

The MFA call factor is now Generally Available (GA).

Bugs Fixed in 2018.28

  • Users received an incorrect error message when using the System Log API and specifying a sort order with an unbounded until statement. (OKTA-175411)

  • Under certain circumstances, the System Log API did not return events on the first query, but did on subsequent queries. (OKTA-174660)

Previously Released Early Access Features 2018.28 Update

The following features have already been released as Early Access. To enable them, contact Support (opens new window).

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

2018.27

Change Expected in Preview Orgs Rollout to Production Orgs Expected to Start
System Log API is Generally Available (GA) July 5, 2018 July 9, 2018
Bugs Fixed in 2018.27 July 5, 2018 July 9, 2018
Previously Released Early Access Features 2018.27 Update Available now Available now

System Log API is Generally Available (GA)

The System Log API is now Generally Available. Developers of new projects are strongly recommended to use this in lieu of the Events API.

Bugs Fixed in 2018.27

  • Users who clicked an Activation Link for an Okta Verify factor that had already been activated would get back an HTTP 500 error. (OKTA-146511)
  • Attempting to add more than the maximum number of zones via the Zones API would result in an HTTP 500 error. (OKTA-175991)

Previously Released Early Access Features 2018.27 Update

The following features have already been released as Early Access. To enable them, contact Support (opens new window).

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

2018.25

Change Expected in Preview Orgs Rollout to Production Orgs Expected to Start
Better /userinfo Errors June 20, 2018 June 25, 2018
Bugs Fixed in 2018.25 June 20, 2018 June 25, 2018
Previously Released Early Access Features 2018.25 Update Available now Available now

Better /userinfo Errors

The following information has been added to the userinfo endpoint's error response:

  • authorization_uri
  • realm
  • resource
  • a list of required scopes in the scope parameter

Bugs Fixed in 2018.25

  • In certain situations, if a call was made to the OAuth 2.0/OIDC /authorize endpoint with response_mode set to okta_post_message, an HTTP 500 error would return. (OKTA-175326)
  • Removing all permissions on a schema attribute would return a READ_ONLY permission. The response now correctly contains a READ_WRITE permission. (OKTA-173030)
  • If an Authorization Server's redirect_uri was too long, an HTTP 500 error would return. (OKTA-171950)
  • The phoneExtension property would not be returned in GET requests to the Factors API's catalog endpoint. (OKTA-108859)

Previously Released Early Access Features 2018.25 Update

The following features have already been released as Early Access. To enable them, contact Support (opens new window).

Early Access Features Available Now
Custom URL Domains
Custom Okta-hosted Sign-In Page
Custom Error Page
Linked Objects API
Token Management API
System Log API
User Consent for OAuth 2.0 and OpenID Connect Flows

2018.24

Change Expected in Preview Orgs Rollout to Production Orgs Expected to Start
User Login Pattern Validation June 13, 2018 June 18, 2018
Bugs Fixed in 2018.24 June 13, 2018 June 18, 2018
Previously Released Early Access Features 2018.24 Update Available now Available now

User Login Pattern Validation

A user's login no longer needs to be in the form of an email address. Instead the login is validated against a pattern property stored in the User Schema, which can be set to certain Regular Expressions. If no pattern is set, the default validation requires email addresses. More information can be found in the User and Schema API references.

Bugs Fixed in 2018.24

  • Queries to the /logs endpoint with a since parameter value of less than 1 minute ago would return a 500 error. (OKTA-174239)
  • It was possible to set an access policy rule with a refreshTokenWindowMinutes value of 0 (infinite). (OKTA-171891)
  • The System Log would not display OpenID Connect App assignment and un-assignment events. (OKTA-168223)

Previously Released Early Access Features 2018.24 Update

The following features have already been released as Early Access. To enable them, contact Support (opens new window).

Early Access Features Available Now
Custom URL Domains
Custom Okta-hosted Sign-In Page
Custom Error Page
Linked Objects API
Token Management API
System Log API
User Consent for OAuth 2.0 and OpenID Connect Flows

2018.23

Change Expected in Preview Orgs Rollout to Production Orgs Expected to Start
Factors API Now Supports U2F June 6, 2018 June 11, 2018
Network Selection Modes Deprecated June 6, 2018 June 11, 2018
Better Signing Key Errors June 6, 2018 June 11, 2018
Previously Released Early Access Features 2018.23 Update Available now Available now

Factors API Now Supports U2F

Enrollment, activation, and verification of U2F factors are now supported in the Factors API.

Network Selection Modes Deprecated

Two deprecated network selection modes (ON_NETWORKand OFF_NETWORK) have been removed from the Network Condition Object. They have been replaced by the ZONE type.

Better Signing Key Errors

If signing keys cannot be generated for a new Authorization Server, a more descriptive error will be returned.

Previously Released Early Access Features 2018.23 Update

The following features have already been released as Early Access. To enable them, contact Support (opens new window).

Early Access Features Available Now
Custom URL Domains
Custom Okta-hosted Sign-In Page
Custom Error Page
Linked Objects API
Token Management API
System Log API
User Consent for OAuth 2.0 and OpenID Connect Flows

2018.22

Change Expected in Preview Orgs Rollout to Production Orgs Expected to Start
New Session Token Behavior is in Early Access May 30, 2018 June 4, 2018
System Log Events for New Device Notification Emails May 30, 2018 June 4, 2018
Bugs Fixed in 2018.22 May 30, 2018 June 4, 2018
Previously Released Early Access Features 2018.22 Update Available now Available now

New Session Token Behavior is in Early Access

If a user has a valid session and passes a sessionToken, this sessionToken will override any existing session cookie. If the user has a valid session but passes an invalid sessionToken, then their existing session will be invalidated. Currently, if a user has a valid session and passes a sessionToken, the sessionToken will be ignored. If this feature is not enabled, the current behavior will continue.

System Log Events for New Device Notification Emails

New device notification email events will now appear in the System Log.

Bugs Fixed in 2018.22

  • Default password policy settings were sometimes incorrectly applied when creating a user with a password. (OKTA-127830)
  • The /userinfo endpoint would return an empty JSON object in the response body when using an invalid access token. (OKTA-169553)
  • Some OAuth 2.0/OIDC refresh tokens would expire early. (OKTA-171056)

Previously Released Early Access Features 2018.22 Update

The following features have already been released as Early Access. To enable them, contact Support (opens new window).

Early Access Features Available Now
Custom URL Domains
Custom Okta-hosted Sign-In Page
Custom Error Page
Linked Objects API
Token Management API
System Log API
User Consent for OAuth 2.0 and OpenID Connect Flows

2018.20

Change Expected in Preview Orgs Rollout to Production Orgs Expected to Start
System Log Entry Delay Change May 15, 2018 May 29, 2018
Previously Released Early Access Features 2018.20 Update Available now Available now

System Log Entry Delay Change

Events returned from the /logs endpoint when using the until parameter were previously delayed by up to 1 second. To improve the performance of our System Log, queries to the /logs endpoint that include an until parameter may now return results that are delayed up to 10 seconds. When making requests with an until value that is near real-time, ensure that you allow enough of a buffer as to not miss events (e.g. 20s).

Bug Fixed in 2018.20

  • Group search queries with underscores returned incorrect results. (OKTA-164390)

Previously Released Early Access Features 2018.20 Update

The following features have already been released as Early Access. To enable them, contact Support (opens new window).

Early Access Features Available Now
Custom URL Domains
Custom Okta-hosted Sign-In Page
Custom Error Page
Linked Objects API
Token Management API
System Log API
User Consent for OAuth 2.0 and OpenID Connect Flows

2018.19

Change Expected in Preview Orgs Rollout to Production Orgs Expected to Start
ID Tokens Can Be Refreshed May 9, 2018 May 14, 2018
Custom URL Domains are in Early Access May 9, 2018 May 14, 2018
Custom Okta-hosted Sign-In Page is in Early Access May 9, 2018 May 14, 2018
Custom Error Page is in Early Access May 9, 2018 May 14, 2018
Bugs Fixed in 2018.19 May 9, 2018 May 14, 2018
Previously Released Early Access Features 2018.19 Update Available now Available now

ID Tokens Can Be Refreshed

OpenID Connect ID tokens can now be retrieved using a refresh token. For more information, see our Open ID Connect Reference.

Custom URL Domains are in Early Access

You can customize your Okta org by replacing the Okta domain name with a custom URL domain name that you specify. For example, if the URL of your Okta org is https://${yourOktaDomain}, you can configure a custom URL for the org such as https://id.example.com. For details, see the Configure a custom URL domain (opens new window).

Custom Okta-hosted Sign-In Page is in Early Access

You can customize the text and the look and feel of the Okta-hosted sign-in page using form controls and an embedded HTML editor. When used together with custom URL domain (opens new window) (required) and custom Okta-hosted error page, this feature offers a fully customized end-user sign-in experience hosted by Okta. For details, see Configure a custom Okta-hosted sign-in page.

Custom Error Page is in Early Access

You can customize the text and the look and feel of error pages using an embedded HTML editor. When used together with custom URL domain (opens new window) (required) and custom Okta-hosted sign-in page, this feature offers a fully customized error page. For details, see Configure a custom error page.

Bugs Fixed in 2018.19

  • Delays were experienced when deleting users. As a result of the fix, one will notice a period of time between when the deletion was initiated and when it completes. During the period, the user will still be visible, but the deletion cannot be reversed. (OKTA-157884)

  • OAuth 2.0 and OIDC requests made with redirect URLs that contained underscores in the domain name would result in an error. (OKTA-167483)

Previously Released Early Access Features 2018.19 Update

The following features have already been released as Early Access. To enable them, contact Support (opens new window).

Early Access Features Available Now
Linked Objects API Is in Early Access (EA)
Token Management API Is in Early Access (EA)
System Log API Is in Early Access (EA)
User Consent for OAuth 2.0 and OpenID Connect Flows Is in Early Access (EA)

2018.18

Change Expected in Preview Orgs Rollout to Production Orgs Expected to Start
Authentication Object for Step-up Authentication Is in Early Access May 2, 2018 May 7, 2018
New Version of the Okta Sign-In Widget Available Now Available Now
Bug Fixed in 2018.18 May 2, 2018 May 7, 2018
Previously Released Early Access Features 2018.18 Update Available now Available now

Authentication Object for Step-up Authentication Is in Early Access

During SP-initiated or IdP-initiated authentication, use the Authentication Object to represent details that the target resource is using.

The Authentication Object is an Early Access feature.

New Version of the Okta Sign-In Widget

Version 2.8.0 of the Okta Sign-In Widget (opens new window) provides new features, notable changes, and bug fixes. For details, visit the okta-signin-widget repository (opens new window).

Bug Fixed in 2018.18

If the configured default IdP was set to inactive, Okta still used the inactive IdP as the primary endpoint for user authentications, causing authentications to fail. (OKTA-137758)

Previously Released Early Access Features 2018.18 Update

The following features have already been released as Early Access. To enable them, contact Support (opens new window).

Early Access Features Available Now
Linked Objects API Is in Early Access (EA)
Token Management API Is in Early Access (EA)
System Log API Is in Early Access (EA)
User Consent for OAuth 2.0 and OpenID Connect Flows Is in Early Access (EA)

2018.17

Change Expected in Preview Orgs Rollout to Production Orgs Expected to Start
Bugs Fixed in 2018.17 April 24, 2018 May 1, 2018
Previously Released Early Access Features 2018.17 Update Available now Available now

Bugs Fixed in 2018.17

  • If an incorrect appInstanceId was supplied as the IdP parameter in a request to the /authorize endpoint, an HTTP 500 error was thrown. (OKTA-166417)

  • When Okta parsed login names it failed to support addresses enclosed in double quotes as described in RFC 3696 (opens new window). (OKTA-164092)

Previously Released Early Access Features 2018.17 Update

The following features have already been released as Early Access. To enable them, contact Support (opens new window).

Early Access Features Available Now
Linked Objects API Is in Early Access (EA)
Token Management API Is in Early Access (EA)
System Log API Is in Early Access (EA)
User Consent for OAuth 2.0 and OpenID Connect Flows is in Early Access (EA)

2018.15

Change Expected in Preview Orgs Rollout to Production Orgs Expected to Start
Enhanced Feature: API Support for Assigning App Instance to App Admins April 11, 2018 April 15, 2018
Bug Fixed in 2018.15 April 11, 2018 April 16, 2018
Previously Released Early Access Features 2018.15 Update Available now Available now

Enhanced Feature: API Support for Assigning App Instance to App Admins

You can add an app instance target to an APP_ADMIN role assignment via the API. Previously an app instance target could be added to the role assignment using the Okta administrators UI only.

When you assign an app instance target to this role assignment, the scope of the role assignment changes from all app targets to just the specified target. Thus you can use this feature to create different APP_ADMIN role assignments for different apps in your org.

For details, visit the Roles API documentation.

Bug Fixed in 2018.15

This fix applies if the MFA soft lock for delegated authentication feature is enabled. When a user made multiple failed MFA attempts and was locked out, the user status was updated to ACTIVE instead of the correct value, LOCKED_OUT. (OKTA-164900)

Previously Released Early Access Features 2018.15 Update

The following features have already been released as Early Access. To enable them, contact Support (opens new window).

Early Access Features Available Now
Linked Objects API Is in Early Access (EA)
Token Management API Is in Early Access (EA)
System Log API Is in Early Access (EA)
User Consent for OAuth 2.0 and OpenID Connect Flows is in Early Access (EA)

2018.14

Change Expected in Preview Orgs Rollout to Production Orgs Expected to Start
Linked Objects API in Early Access (EA) April 4, 2018 April 9, 2018
Client SDKs Version 1.0 Available Now Available Now
Bug Fixed for 2018.14 April 4, 2018 April 9, 2018
Previously Released Early Access Features Available now Available now

Linked Objects API in Early Access (EA)

Users have relationships to each other, like manager and subordinate or customer and sales representative. You can create users with relationships by using the Linked Objects API.

Okta allows you to create up to 200 linked object definitions. These definitions are one-to-many:

  • A manager has many subordinates
  • A sales representative has many customers
  • A case worker has many clients

Of course, most organizations have more than one manager or sales representative. You can create the linked object definition once, then assign the primary relationship to as many users as you have people in that relationship.

You can assign the associated relationship for a single primary user to as many users as needed. The associated user can be related to only one primary per linked object definition. But a user can be assigned to more than one linked object definition.

For more details:

Client SDKs Version 1.0

We published the 1.0 version of the following client SDKs:

Visit each SDK for a complete list of new features, enhancements, and bug fixes.

Bug Fixed for 2018.14

  • If someone was able to obtain a user's activation email or password reset email and attempt to log in before the real user completed logging in, that person could access the account at the same time as the real user. (OKTA-85691)

Previously Released Early Access Features

The following features have already been released as Early Access. To enable them, contact Support (opens new window).

Early Access Features Available Now
Token Management API Is in Early Access (EA)
System Log API Is in Early Access (EA)
User Consent for OAuth 2.0 and OpenID Connect Flows is in Early Access (EA)

2018.12

Change Expected in Preview Orgs Rollout to Production Orgs Expected to Start
Change to App Variable Name Incrementing March 21, 2018 March 26, 2018
Token Management API Is in Early Access (EA) March 21, 2018 March 26, 2018
System Log API Is in Early Access (EA) Available Now Available Now
Password Imports with Salted SHA-256 Algorithm is in Early Access (EA) Available Now Available Now
Bug Fixed for 2018.12 March 21, 2018 March 26, 2018

Change to App Variable Name Incrementing

When creating multiple instances of the same app, each instance of the app has a unique Variable Name. This Variable Name is used as part of the Okta Expression Language. Previously each instance was incrementally numbered (salesforce_1, salesforce_2, etc), but going forward each instance will instead have a 7-character alphanumeric string appended to its Variable Name. To find your app's Variable Name, go into the Profile Editor for that app. This change only affects newly created apps.

Token Management API Is in Early Access (EA)

Use the Token Management API to view and revoke OAuth 2.0 and OpenID Connect refresh tokens by end user, Custom Authorization Server, or client app.

Bug Fixed for 2018.12

  • GET requests to the /authorize endpoint with response_mode=form_post would return an HTML page with a title <span>. (OKTA-162709)

2018.11

Change Expected in Preview Orgs Rollout to Production Orgs Expected to Start
API Support for IdP-initiated Authentication March 14 March 19
New Powershell Module for TLS 1.2 Compatibility Available Now Available Now
Rate Limit for System Log Increased Available Now Available Now
New Version of Okta Sign-in Widget Available Now Available Now
System Log API Is in Early Access (EA) Available Now Available Now
Password Imports with Salted SHA-256 Algorithm is in Early Access (EA) Available Now Available Now
Bugs Fixed for 2018.11 March 14, 2018 March 19, 2018

API Support for IdP-initiated Authentication

Use this feature to allow a client to specify the application right away during an authentication request, instead of taking the user through "step-up" authentication in a separate request. Documentation

New Powershell Module for TLS 1.2 Compatibility

The new version of Okta's Powershell module is compatible with TLS 1.2. Documentation (opens new window)

Rate Limit for System Log Increased

The rate limit for GET requests to /api/v1/logs has been increased from 60 per minute to 120. Documentation

New Version of Okta Sign-in Widget

Version 2.7.0 of the Okta Sign-in Widget provides new features, notable changes, and bug fixes. For details, visit the okta-signin-widget repository (opens new window).

Bugs Fixed for 2018.11

  • An incorrect error message was returned when a blank password was specified in a password reset request. (OKTA-144982)
  • If administrators in an org with the Developer Console enabled used the Classic user interface instead, and had no apps assigned, they couldn't access their own user home page. (OKTA-152324)
  • For the System Log API, the displayName in the Target object was set to Unknown if the eventType was user.authentication.sso and if the value didn't exist in the profile editor. This behavior matches the behavior in /events. (OKTA-156484)

2018.10

Change Expected in Preview Orgs Rollout to Production Orgs Expected to Start
API Access Management is Generally Available (GA) in Production Available now March 12, 2018
System Log API Is in Early Access (EA) March 7, 2018 March 12, 2018
Password Imports with Salted SHA-256 Algorithm is in Early Access (EA) March 7, 2018 March 12, 2018
New Parameter for Authentication with Okta Verify with Auto-Push March 7, 2018 March 12, 2018
System Log Changes for 2018.10 March 7, 2018 March 12, 2018
Bugs Fixed for 2018.10 March 7, 2018 March 12, 2018

API Access Management is Generally Available (GA) in Production

Secure your APIs with API Access Management, Okta's implementation of the OAuth 2.0 authorization framework. API Access Management uses the Okta Identity platform to enable powerful control over access to your APIs. API Access Management can be controlled through the administrator UI as well as a rich set of APIs for client, user, and policy management.

Generally Available (GA) in preview orgs since February 7, 2018, API Access Management is scheduled to be GA in production orgs starting March 12, 2018.

For more information, see OAuth 2.0 and Okta.

System Log API is in Early Access (EA)

The Okta System Log records system events related to your organization in order to provide an audit trail that can be used to understand platform activity and to diagnose problems.

The Okta System Log API provides near real-time read-only access to your organization's system log and is the programmatic counterpart of the System Log UI (opens new window).

Often the terms "event" and "log event" are used interchangeably. In the context of this API, an "event" is an occurrence of interest within the system and "log" or "log event" is the recorded fact.

Notes:

Password Imports with Salted SHA-256 Algorithm is in Early Access (EA)

You can use the salted SHA-256 hash type when importing passwords.

New Parameter for Authentication with Okta Verify with Auto-Push

We have added an optional URL parameter, autoPush that allows Okta to store the user's Auto-Push preference when verifying Okta Verify with Auto-Push. This parameter is only necessary when implementing custom login flows that do not use the Okta Sign-In Widget.

System Log Changes for 2018.10

  • If a query to /logs timed out, an HTTP 504 error was returned. Now an HTTP 500 error will be returned. This aligns /logs error responses with other Okta APIs, and ensures implementation details are not leaked to API consumers. (OKTA-159642)
  • The following changes to error codes related to the system log were made to make them consistent with Okta error codes:
    • MEDIA_TYPE_NOT_ACCEPTED_EXCEPTION replaced by UNSUPPORTED_MEDIA_TYPE
    • OPP_INVALID_PAGINATION_PROPERTIES replaced by INVALID_PAGING_EXCEPTION
    • OPP_INVALID_SCIM_FILTER replaced by INVALID_SEARCH_CRITERIA_EXCEPTION

Bugs Fixed for 2018.10

  • GET requests to list 200 or more apps were taking a long time to complete. (OKTA-158391)
  • Invalid IP addresses in the X-Forwarded-For header caused a null pointer exception (HTTP 500 NullPointerException) during primary authentication. (OKTA-159414)
  • List User with Search requests in preview orgs failed to return pagination links. (OKTA-160424)

2018.09

Change Expected in Preview Orgs Rollout to Production Orgs Expected to Start
API Access Management is Generally Available in Preview February 7, 2018 March 12, 2018
User Consent for OAuth 2.0 and OpenID Connect Flows in Early Availability (EA) February 28, 2018 March 5, 2018
Sessions API Supports HTTP Header Prefer February 28, 2018 March 5, 2018
User Schema API Allows Nullable firstName, lastName February 28, 2018 March 5, 2018
Improved Response Mode for OAuth 2.0 and OpenID Connect Requests February 28, 2018 March 5, 2018
Change to /authorize Response for prompt for OAuth 2.0 and OpenID Connect Requests February 28, 2018 March 5, 2018
Improved System Log Behavior for Date Queries February 28, 2018 March 5, 2018
System Log Message Changes Related to Authorization Servers February 28, 2018 March 5, 2018
Bugs Fixed for 2018.09 February 28, 2018 March 5, 2018

A consent represents a user's explicit permission to allow an application to access resources protected by scopes. As part of an OAuth 2.0 or OpenID Connect authentication flow, you can prompt the user with a page to approve your app's access to specified resources.

Consent grants are different from tokens because a consent can outlast a token, and there can be multiple tokens with varying sets of scopes derived from a single consent. When an application comes back and needs to get a new access token, it may not need to prompt the user for consent if they have already consented to the specified scopes. Consent grants remain valid until the user manually revokes them, or until the user, application, authorization server or scope is deactivated or deleted.

To configure an authorization or authentication flow to include a user consent page:

  1. Verify that you have the API Access Management feature enabled, and request that User Consent also be enabled.

  2. Create an app via the Apps API with the appropriate values for tos_uri, policy_uri, and consent_method. (Details)

    Note: You can also configure an existing app in the administrator UI: Applications > [Application Name] > General > User Consent.

  3. Ensure that your authentication or authorization flow is configured properly. The combination of prompt in the /authorize request, consent_method set on the app in the previous step, and consent, a property set on scopes, controls whether a user consent window is displayed during the authentication flow. Details

Sessions API Supports HTTP Header Prefer

Okta now supports the HTTP Header Prefer (opens new window) in the Sessions API for refreshing sessions. You can extend the session lifetime, but skip any processing work related to building the response body.

Example Request

curl -v -X POST \
-H "Accept: application/json" \
-H "Content-Type: application/json" \
-H "Authorization: SSWS ${api_token}" \
"https://${yourOktaDomain}/api/v1/sessions/me/refresh"

Note: me can also be an ID.

Example Response

HTTP/1.1 204 No Content
Preference-Applied: return=minimal

User Schema API Allows Nullable firstName, lastName

You can set firstName or lastName to be nullable in the User Profile Base sub-schema. These properties are defined in a profile sub-schema with the resolution scope #base.

Improved Response Mode for OAuth 2.0 and OpenID Connect Requests

For the form_post response mode, we have reduced the HTML content returned in an OpenID Connect or OAuth 2.0 request. Now the response is only a form containing the requested tokens (access token, ID token, or both) and JavaScript to post the form.

Change to /authorize Response for prompt for OAuth 2.0 and OpenID Connect Requests

If you set prompt=none for a request on /authorize and the maximum age before sign-in is required (max_age) is exceeded, an error is returned. This ensures the safest possible result when these two settings contradict each other.

This applies to /authorize with either the Okta Org Authorization Server or a Custom Authorization Server (which requires API Access Management).

Example: Old Message Format

{
    "errorCode": "E0000001",
    "errorSummary": "Api validation failed: com.saasure.core.services.user.InvalidUserProfileException: Could not create user due to invalid profile: com.saasure.framework.validation.util.SimpleErrors: 1 errors\nError in object 'newUser': codes [password.passwordRequirementsNotMet.newUser,password.passwordRequirementsNotMet]; arguments [Password requirements: at least 8 characters, a lowercase letter, an uppercase letter, a number, no parts of your username.]; default message [Password requirements were not met. Password requirements: at least 8 characters, a lowercase letter, an uppercase letter, a number, no parts of your username.]",
    "errorLink": "E0000001",
    "errorId": "oaecNfS38enQ8KtWDvNfusWRw",
    "errorCauses": [
        {
            "errorSummary": "Password requirements were not met. Password requirements: at least 8 characters, a lowercase letter, an uppercase letter, a number, no parts of your username."
        }
    ]
}

Example: New Message Format

{
    "errorCode": "E0000001",
    "errorSummary": "Api validation failed: com.saasure.core.services.user.InvalidUserProfileException: Could not create user due to invalid profile: com.saasure.framework.validation.util.SimpleErrors: 3 errors\nField error in object 'newUser' on field 'password': rejected value [aaaa]; codes [password.minlength.newUser.password,password.minlength.password,password.minlength.java.lang.String,password.minlength]; arguments [8]; default message [Password requirements: at least 8 characters.]\nField error in object 'newUser' on field 'password': rejected value [aaaa]; codes [password.uppercase.newUser.password,password.uppercase.password,password.uppercase.java.lang.String,password.uppercase]; arguments [Password requirements: at least 0 characters, an uppercase letter.]; default message [Password requirements: at least 0 characters, an uppercase letter.]\nField error in object 'newUser' on field 'password': rejected value [aaaa]; codes [password.number.newUser.password,password.number.password,password.number.java.lang.String,password.number]; arguments [Password requirements: at least 0 characters, a number.]; default message [Password requirements: at least 0 characters, a number.]",
    "errorLink": "E0000001",
    "errorId": "oaeGZUg95w6SK2GbA44cXgtvA",
    "errorCauses": [
        {
            "errorSummary": "password: Passwords must be at least 8 characters in length",
            "reason": "LENGTH_MINIMUM",
            "location": "credentials.password.value",
            "locationType": "body",
            "domain": "user"
        },
        {
            "errorSummary": "password: Password requirements: at least 0 characters, an uppercase letter.",
            "reason": "UPPER_CASE_REQUIRED",
            "location": "credentials.password.value",
            "locationType": "body",
            "domain": "user"
        },
        {
            "errorSummary": "password: Password requirements: at least 0 characters, a number.",
            "reason": "NUMBER_REQUIRED",
            "location": "credentials.password.value",
            "locationType": "body",
            "domain": "user"
        }
    ]
}

If you don't want these changes, contact Support (opens new window) to opt out.

Improved System Log Behavior for Date Queries

  1. For /logs, the request parameters since and until require the RFC 3339 Internet Date/Time Format profile of ISO 8601 (opens new window). This allows queries to more accurately target date ranges.

  2. For /logs, the maximum page size is 1,000 messages (limit=1000). The default remains at 100.

The following message changes apply to either the Okta Org Authorization Server or a Custom Authorization Server including default (which requires API Access Management), or both, as indicated in each section.

Simplified Failure Messages from /authorize Requests for /events System Log

The existing messages app.oauth2.authorize_failure, app.oauth2.as.authorize_failure and app.oauth2.as.authorize.scope_denied_failure replace these messages:

  • app.oauth2.authorize.access_denied
  • app.oauth2.authorize.invalid_client_id
  • app.oauth2.authorize.invalid_cache_key
  • app.oauth2.authorize.no_existing_session
  • app.oauth2.authorize.login_failed
  • app.oauth2.authorize.mismatched_user_in_cache_and_session
  • app.oauth2.authorize.user_not_assigned
  • app.oauth2.authorize.scope_denied
  • app.oauth2.as.authorize.warn_failure
  • app.oauth2.as.authorize.scope_denied

Details about the nature of the failure are included, so no information has been lost with this simplification.

These system log changes affect responses from requests that involve either the Okta Org Authorization Server or a Custom Authorization Server including default.

Simplified Failure Messages from /token Requests for /events System Log

Instead of supplying two different messages for token grant failures on /token, the existing message app.oauth2.as.authorize.token.grant_failure replaces these messages:

  • app.oauth2.as.token.grant.warn_failure
  • app.oauth2.as.token.grant.scope_denied_failure

This system log change affects responses from requests that involve a Custom Authorization Server including default.

Simplified Success Messages from /token Requests for /events System Log

Instead of supplying a different message for ID token and access token generation, there's just one message for each. The ID token or access token minted is included in the message as it was previously.

  1. The existing message app.oauth2.authorize.implicit_success replaces:

    • app.oauth2.authorize.implicit.id_token_success
    • app.oauth2.authorize.implicit.access_token_success
  2. The existing message app.oauth2.as.authorize.implicit_success replaces:

    • app.oauth2.as.authorize.implicit.id_token_success
    • app.oauth2.as.authorize.implicit.access_token_success

The _success messages weren't being written to the System Log previously, but are now.

These system log changes affect responses from requests that involve either the Okta Org Authorization Server or a Custom Authorization Server including default.

Simplified Messages from /token Requests for /logs System Log

Instead of supplying a different message for ID token and access token generation, there's just one message for each. The ID token or access token minted is included in the message as it was previously.

  1. The existing message app.oauth2.authorize.implicit replaces:

    • app.oauth2.authorize.implicit.id_token
    • app.oauth2.authorize.implicit.access_token
  2. The existing message app.oauth2.as.authorize.implicit replaces:

    • app.oauth2.as.authorize.implicit.id_token
    • app.oauth2.as.authorize.implicit.access_token

These system log changes affect responses from requests that involve either the Okta Org Authorization Server or a Custom Authorization Server, including default.

Bugs Fixed for 2018.09

The following bugs have been fixed and are expected in preview orgs February 28, 2018 and production orgs starting March 5, 2018.

  • If a user had a status of ACTIVE and had never signed in, and an API call reset the user's password, the user's status was incorrectly changed from ACTIVE to PROVISIONED, instead of the expected RECOVERY. (OKTA-154024)
  • If -admin was incorrectly included in the domain name during initialization of an OktaAuth object (opens new window), no error was returned. (OKTA-156927)
  • If a user was created with a password, that password wasn't considered as part of their password history. (OKTA-158966)

2018.07

Feature Enhancement

The following feature enhancement is expected in preview orgs February 14, 2018, and in production orgs on February 27, 2018.

Keystore Rollover Events Now Logged

OAuth key store rollover events are now included in both the Events and System Log APIs.

Bug Fixed

The following bug has been fixed and is expected in preview orgs February 14, 2018 and production orgs starting February 27, 2018.

  • The error message "Exception while persisting IdpAppUser" wasn't available in the System Log API. (OKTA-153604)

2018.06

Feature Enhancements

Feature Enhancement Expected in Preview Orgs Expected in Production Orgs
API Access Management is Generally Available in Preview February 7, 2018 starting March 12, 2018
New Administrator Role for API Access Management February 7, 2018 starting February 12, 2018
New and Changed Messages for the System Log February 7, 2018 starting February 12, 2018

API Access Management is Generally Available in Preview

Secure your APIs with API Access Management, Okta's implementation of the OAuth 2.0 authorization framework. API Access Management uses the Okta Identity platform to enable powerful control over access to your APIs. API Access Management can be controlled through the administrator UI as well as a rich set of APIs for client, user, and policy management.

For more information, see OAuth 2.0 and Okta.

New Administrator Role for API Access Management

If you have API Access Management enabled, you can use a dedicated administrator's role for API Access Management: the API Access Management Admin role. Use this role to manage custom authorization servers and related tasks:

  • Create and edit authorization servers, scopes, custom claims, and access policies
  • Create and edit OAuth 2.0 and OpenID Connect client apps
  • Assign users and groups to OAuth 2.0 and OpenID Connect client apps

To change the role assigned to a user, use the Administrator Roles API or visit Security > Administrators in the administrator UI.

New and Changed Messages for the System Log

We've added a new message and improved an existing one in the System Log (/api/v1/logs):

  • A message is now written to the System Log when password credentials fail. Previously this message was written only to /api/v1/events.
  • The System Log message policy.rule.deactivated specifies in the Debug Context when the cause of a rule being disabled is that all the network zones for that rule have been deleted.

Bug Fixed

The following bug has been fixed and is expected in preview orgs February 7, 2018 and production orgs starting February 12, 2018.

  • A spurious next link from the response headers was returned by a policy get operation (GET {url} /api/v1/policies). (OKTA-152522)

2018.05

Feature Enhancements

Feature Enhancement Expected in Preview Orgs Expected in Production Orgs
App User Schema API is Generally Available Available Now Available Now
Special HTML Characters in state for okta_post_message January 31, 2018 February 7, 2018
Custom Scopes in Metadata Endpoints January 31, 2018 February 7, 2018
Improved Enforcement of Authorization Server Policies January 31, 2018 February 7, 2018
Functions for Including Groups in Tokens January 31, 2018 February 7, 2018
New System Log Messages January 31, 2018 February 7, 2018
New Version of the Sign-In Widget Available Now Available Now

Generally Available: App User Schema API

Use the App User Schema API to work with App User profiles, typically for apps that have features for provisioning users.

Special HTML Characters in state for okta_post_message

You can include HTML special characters in the state parameter for okta_post_message. Note that state in the main request body already allows these characters.

Custom Scopes in Metadata Endpoints

You can specify whether or not to include custom scopes in the metadata endpoints for OAuth 2.0 and OpenID Connect. Existing custom scopes are not exposed by default. Set the metadataPublish attribute to ALL_CLIENTS to change the behavior.

Improved Enforcement of Authorization Server Policies

When a client application tries to redeem an authorization token from a refresh token issued by a custom authorization server, policies are evaluated again. This ensures any changes since the time the refresh token was issued are checked.

Functions for Including Groups in Tokens

Use the new EL functions Group.contains, Group.startsWith, and Group.endsWith to define a set of dynamic groups to be included in tokens minted from Okta's authorization servers.

These functions complement the existing EL function getFilteredGroups which helps you create a static list of groups for inclusion in a token.

New System Log Messages

User account updates have two new events written to the system log ( /api/v1/events and /api/v1/logs):

  • The user.account.unlock_by_admin event complements the existing user.account.unlock event which is triggered only by self-service unlock or automatic unlock. The user.account.unlock_by_admin event is triggered when an administrator unlocks an account.
  • The user.account.update_primary_email event is triggered only when a primary email is updated. It's not triggered by profile sync or other automated processes.

New Version of the Sign-In Widget

Version 2.6.0 of the Okta Sign-In Widget (opens new window) is available. Check out the new features and bug fixes!

Bugs Fixed

The following bugs have been fixed and are expected in preview orgs January 31, 2018 and production orgs starting February 7, 2018.

  • Client applications could redeem an access token from a refresh token if it contained a deleted scope. (OKTA-154738)
  • The exception thrown when creating a zone without the correct features enabled was incorrect 501: unsupported operation. Now the correct exception is thrown: 401: You do not have permission to access the feature you are requesting. (OKTA-154940)
  • Requests to /api/v1/authn with deviceToken in the body of the request incorrectly prompted the user for MFA, even after successfully verifying the factor the first time, if:
    • The org had MFA enabled ( Sign On Policy > Prompt for Factor > Per Device ).
    • The user was assigned to an app that had password sync enabled. (OKTA-156826)

2018.03

Feature Enhancements

Feature Enhancement Expected in Preview Orgs Expected in Production Orgs
App User Schema API is Generally Available Available Now February 13, 2017

Generally Available: App User Schema API

Use the App User Schema API to work with App User profiles, typically for apps that have features for provisioning users.

2018.02

Feature Enhancements

Feature Enhancement Expected in Preview Orgs Expected in Production Orgs
App User Schema API is Generally Available January 10, 2018 February 13, 2017
SHA-256 Certificates for New SAML 2.0 Apps is Generally Available Available Now January 10, 2018

Generally Available: App User Schema API

Use the App User Schema API to work with App User profiles, typically for apps that have features for provisioning users.

Generally Available: SHA-256 Certificates for SAML 2.0 Apps

When you create a SAML 2.0 app in Okta, the app is created with SHA-256 signed public certificates. Certificates for existing SAML 2.0 apps aren't changed. To update an existing app, use these instructions.

Bug Fixes

The following bugs have been fixed, and are expected in preview orgs starting January 10, 2018, and in production orgs starting January 16, 2018.

  • Network zones couldn't be deleted if they were associated with a sign-on policy, even after the policy has been deleted. (OKTA-150747)
  • Results returned from the Users API incorrectly reported the status of some users who were mastered by Active Directory. The statuses PASSWORD_RESET or LOCKED_OUT were reported as ACTIVE. (OKTA-153214, OKTA-151861)

2017.52

Feature Enhancements

Feature Enhancement Expected in Preview Orgs Expected in Production Orgs
Token Preview December 28, 2017 January 8, 2017
New values for amr base claim December 28, 2017 January 8, 2017

Token Preview

Configuring an application or integration to use OpenID Connect ID tokens or OAuth 2.0 access tokens can take a lot of trial-and-error. Okta has made it easier to choose configuration settings and see the resulting tokens in the Token Preview tab of the Authorization Server page: