Virtual Views of Okta not working after Updating to v7.4.7

ISSUE:

Virtual views of Okta are not working after updating to v7.4.7.

SOLUTION:

The Okta custom data source in RadiantOne v7.4.7 has been updated to use the newer SDK. This is the reason why existing virtual views of Okta are not working after updating to v7.4.7.  Any existing data source, orx file, dvx file, or mounted view that was configured for an Okta backend will need to be reconfigured.

Use the new okta2.orx and okta2.dvx included in the updater and update the oktaclient custom data source (or your own if you cloned the default) to delete the apikey property, and add the new apitoken property. Make sure to populate the apitoken property with a valid API Token generated in Okta.

Also, CREATE operations on Okta are currently not supported, only update/delete operations.