On This Page
|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|
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:
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.
- 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)
The following features have already been released as Early Access. To enable them, contact Support.
|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)|