Troubleshooting

Feedback Documentation Feedback Connectivity Documentation Feedback
1

[ InvalidConfigurationException ] [ Possible suggestions ] Ensure the resource mentioned in the Okta URL is correct. The URL resource is //api/v1/users/00u1jw6jffvr3GG395d7/roles/IFIFAX2BIRGUSTQ/targets/catalog/apps/hellofax [ Error details ] Request execution failed. HTTP Error code : 405, Okta Error code : E0000091, errorSummary : The provided role type was not the same as required role type., errorCauses:[].

This is the companion discussion topic for the documentation at https://documentation.sailpoint.com/connectors/okta/help/integrating_okta/troubleshooting.html
2

image
image1104×247 33.9 KB

This still references the CC API. Please update with current API endpoints and the expected key/value pairs.

6

Hi Mark,
Thank you for your input. We’ve created a Jira issue to track the effort and we’ll update the comment thread when it’s been addressed: CONDOCS-6853.

7

It seems that the connector has some optimization enabled and I’m not sure how to change this configuration. When the connector attempts to remove entitlements for a user that is already disabled within Okta, I get the following error message:

[“sailpoint.connector.ConnectorException: [ ConnectorException ] \n [ Error details ] Failed to update the account. [ ConnectorException ] \n [ Error details ] Skipping the provisioning for Okta account id <> as it is in DEPROVISIONED status”]

It would be nice to know if this is expected, and if so, if there is a way to remove entitlements even when the Okta account is already deprovisioned.