IDN SuccessFactor Attribute Mapping

Identity Security Cloud (ISC) ISC Discussion and Questions
,
1

I see a similar question was posted before with no responses (IDN SuccessFactor Integration - #2) so I’m starting a new thread to hopefully clarify the details.

We need to confirm the specific attribute mapping for the data attributes in the standard connector. Example: The connector has an attribute called “FormalName” but we need to know specifically the path in the SOAP call response that is used to map the SuccessFactor value to this attribute (as well as other attributes).

Once we have the attribute mapping we can then work with the HR team to specifically define what screen/attribute within SuccessFactors is being utilized for troubleshooting and compliance.

2

There is no information about that in any SailPoint documentation.

You can create support ticket but cannot guarantee that you get information you are looking for.

This okta documentation might help you to understand the OOTB attributes in SuccessFactors, they do have custom attributes as well.

I don’t think there is FormalName attribute in SuccessFactors, it might be formal_name, SailPoint might have used the variables in their coding without underscores with same SF path.

/person/personal_information/formal_name

Thanks
Krish

1 Like
3

Hi Marks,

You can get the Odata attributes path file your SF team. You have to map only the custom attributes.

Rest of the OOTB attributes no need to provide mapping.

Reach out to Hr tech team they will download a file and share you.

Thanks,
Siva.K

4

Please find the steps to get OData api file from SF

5

This is pretty much the exact issue I’m struggling with and I can’t believe it’s not published with the connector.

The issue is what field in SuccessFactors is mapped to the attribute in the default connector. I can certainly make a best guess, but there’s obviously a mapping and/or logic in the connector that should be publicly available.

Thinking of the testing process - How does anyone guarantee the specific field updated in a screen in SuccessFactors is the “right” field to update. Similar for ongoing support - How do you confirm the specifics of this connector when HR says “it’s right” but the connector brings in different data.

6

Not just SuccessFactors, we don’t have any information over how the connector is built. Did they use APIs or some Protocols to connect to the application. Whenever there is an error, application team does ask me how are you connecting to the application ? I don’t have an answer for that.

I understand that, I have worked on SuccessFactors integration in IDN 2 times so far. Would it help you If I say that, we didn’t use OOTB attributes at all. Configured SF API paths for all attributes. Now we know what we are reading and from which path.

Thanks
Krish

7

We have similar issue. We have used OOTB Successfactor connector to bring in most of the user attributes. It appears that the ISC Connector takes most of the data from PerPersonal schema. ( “uri”: “PerPersonal”,
“type”: “SFOData.PerPersonal”).
The limitation we faced was, we were not able to extend connector to get custom attributes from Successfactor, We had to add additional REST source which we use to read the specific attributes we need. Which also seems to be very controlled approach,

8

It depends on how your SuccessFactors is designed for your org.

In one client, we had custom attributes which we couldn’t bring using OOTB connector which uses (SF API), so used WebService connector to make use of OData API to pull the missing attributes.

Where as in other client, we were able to pull all the attributes using OOTB connector itself.

Thanks
Krish

1 Like
9

This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.