Connector Improvement: Okta connector: Option to deselect child tables
PlannedHello Team,
With the okta connector, we would like to select/deselect objects in the schema tab of the connector.
Currently, for example our requirement needs the below objects (listed at the bottom), but in the connector there is no option for deselecting the child objects, which means that there will be a MAR of millions of records for just one object like 'application_user' (which we dont intend to use the data) for every sync and also each sync starts taking time which in our case goes into 6 days per sync (even though we don't system logs based objects).
Could you please review and let us know by when will the changes be implemented so that okta connector is viable for use?
DEVICE
DEVICE_USER
USERS
GROUPS
APPLICATION_GROUP
APPLICATION
OAUTH_CLIENT_GRANT_TYPE
OAUTH_CLIENT_POST_LOGOUT_REDIRECT_URI
OAUTH_CLIENT_REDIRECT_URI
OAUTH_CLIENT_RESPONSE_TYPE
POLICY
RULE
-
Official comment
Hi Reuben,
I wanted to provide an update on the deselection requirement.
This has been planned, and I will update you when we make this available to the Okta Connector.
We are tentatively targeting to deliver it by Jan'26.
Thank You,
Vishal
Please sign in to leave a comment.
Comments
1 comment