| 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 |
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.
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:
To change the role assigned to a user, use the Administrator Roles API or visit Security > Administrators in the administrator UI.
We've added a new message and improved an existing one in the System Log (/api/v1/logs):
/api/v1/events. 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. The following bug has been fixed and is expected in preview orgs February 7, 2018 and production orgs starting February 12, 2018.
next link from the response headers was returned by a policy get operation (GET {url} /api/v1/policies). (OKTA-152522)