Manage all AccessControls of Salesforce
We are working on Salesforce integration approach. We understood from Salesforce team that they have the below following user access controls on application -
- Permission Sets
- Public Groups
Using OOTB Salesforce Collectors & Connectors, is it possible to collect & manage these controls in RSA ? Because Salesforce integration guide mentions only roles & groups in OOTB collection.
Guide also mention it supports only
Salesforce V37.0 and lower (RSA Identity Governance and Lifecycle 7.0.2 and earlier)
Salesforce V40.0 and lower (RSA Identity Governance and Lifecycle 7.1.0)
Salesforce V44.0 and lower (RSA Identity Governance and Lifecycle 7.1.1)
Are these API versions or plateform version ?
- Access & Change Requests
- Community Thread
- Forum Thread
- Identity G&L
- Identity Governance & Lifecycle
- RSA Identity
- RSA Identity G&L
- RSA Identity Governance & Lifecycle
- RSA Identity Governance and Lifecycle
- RSA IGL
- salesforce connector
Typically what is outlined in the Application Datasheet is what is supported. It would be unusual for the collector or connector to have additional features that are not documented.
The versions listed are the expected endpoint versions of SalesForce. It is possible to specify a lower version than is listed for compatibility with older targets, but you cannot specify a version higher than is supported.
For 7.2.0 you also have the option of using the Generic REST connector and Generic REST collector for SalesForce.
RSA Professional Services can assist you with integrations using the Generic REST collector.
In general, if you want to integrate with the latest version of SalesForce you should anticipate that you may have to upgrade to the latest version of IG&L for full interoperability.
Are there any examples for configuring the REST connector?
This is my current error "Unexpected response content type received. Expected content type is: application/json but received: [text/html; charset=UTF-8]"
I have tried multiple scenarios in the Request Headers area.
There are specific instances where the REST collector fails with this error.
It is also a generic failure of the REST collector where the response is supposed to be a JSON object but is instead a basic http error message (html). For example a 404 in an unexpected place may generate this error.