SuccessFactors : Where does attribute schema filtering happen

Identity Security Cloud (ISC) ISC Discussion and Questions
1

Hi,

We had a query related to SAP SuccessFactors connector -
The client is concerned about the data privacy and concerned where does the filtering of attributes happen based on the account schema(as they don’t want the PII attributes consumed by cloud tenant and then filtered) - as the SAP SuccessFactors connector internally calling SFAPI/ODATA APIs would pull in all the attributes and then filter based on schema.

My understanding on this would be that the VA which has the CCG (containing Enterprise Connector) would be doing this filtering and the data filtering would happen in customer premises before being visible on cloud tenant. Is this understanding correct and is there any documentation on this ?

@colin_mckibben

Before you post in our general IdentityNow (IDN) category, please review other subcategories for a better fit. If you’re posting here regarding UI configuration or Out of the Box Connectors, please visit our Compass Community for assistance. The SailPoint Developer Forum focuses on helping the developer community extend the capabilities of IDN beyond what is provided in the user interface.

2

Hi Aditya,

You are correct. The virtual appliance (VA) is a custom VM image provided by SailPoint and hosted by the customer in their intranet. SailPoint only provides updates for the VA, and doesn’t manage it in any other way. Each connector has a different way of interacting with a source depending on what APIs the source has to offer. I am not familiar with SuccessFactors and how the connector works with it. Based on the connector docs, it looks like the SuccessFactors connector can do the attribute filtering on the source before pulling them into the VA, but I’m not 100% sure on that. Even if a connector has to pull the attributes into the VA and then do the filtering, all of this is happening on the customer’s own infrastructure and within their intranet.