I can't read some attributes in SSFF with a Web Services connector

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

I am trying to read some attributes in the SSFF connector and I am not able to read the “secondLastName” even though I should be able to read it without any problem since the context URL points to the table where this attribute is located.
This is te context URL “/odata/v2/EmpJob?$format=json&$top=1000&$skip=0&$expand=employmentNav/personNav/personalInfoNav”
And i can read “personIdExternal” and “dateOfBirth” like this “employmentNav.personNav.personIdExternal” and “employmentNav.personNav.dateOfBirth”
But i cant with “secondLastName” like this “employmentNav.personNav.personalInfoNav.secondLastName”
SecondLastName
In the image you can see that the route is the correct one “personalInfoNav.secondLastName” but it still doesn’t read it.

2

@Juanisola did you try with following? It should work

employmentNav/personNav/personalInfoNav/secondLastName

Regards,
Shekhar Das

3

When I add the path to the context url it gives me the following error
“sailpoint.connector.ConnectorException: Url: https://api8preview.sapsf.com//odata/v2/EmpJob?$format=json&$top=1000&$skip=0&$expand=employmentNav/personNav/personalInfoNav/secondLastName, Message: 400 : Bad Request, HTTP Error Code: 400”
And when I add the path to the attribute mapping I still don’t read it

4

Try below:

https://api8preview.sapsf.com/odata/v2/EmpJob?$select=employmentNav/personNav/personalInfoNav/secondLastName&$format=json&$top=1000&$skip=0

Regards,
Shekhar Das

1 Like
5

By the way you have double // before odata/v2 in your context URL JFYI.

1 Like
6

Are you trying to map this information in the Response Mapping section to assign it to an account schema attribute? If so, you can try this:

employmentNav.personNav.personalInfoNav.results[*].secondLastName

You can also take the response body and put it into JSONPath to test out the syntax needed to get the attributes you are looking for.

2 Likes
7

Apparently adding the results[] the mapping is working, thank you very much to both.
I don’t know if it has anything to do with it but all the attributes that were failing, I had to navigate through more than 3 tables. those that went through less than 2 tables were mapped correctly without the results[

2 Likes
8

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