When we are doing test connection form MS Azure to successfactors getting error as Invalid credentials

Question

Testing connection to SuccessFactors to Azure AD User Provisioning

You appear to have entered invalid credentials. Please confirm you are using the correct information for an administrative account.

Error code: InvalidCredentials

Details: No persons returned from SuccessFactors. Ensure that the account used has sufficient permissions to query the PerPerson entity.

Request-id: 782fc0cc-686b-4415-a0f7-b40f77917ead

Please note the API user permissions and IP ranges has been maintained properly

Answer 1

Hi,

It seems like you are missing a required attribute is missing or not populated for a user. An important thing to consider when setting up provisioning be to review and configure the attribute mappings and workflows that define which user (or group) properties flow from Azure AD to the application. This includes setting the “matching property” that be used to uniquely identify and match users/groups between the two systems.

Check this page for detailed information on setthing up the sync - [https://learn.microsoft.com/en-us/azure/active-directory/app-provisioning/customize-application-attributes

Hope this helps.

JS

==

Please Accept the answer if the information helped you. This will help us and others in the community as well.

Answer 2

hi Marshaljs,

When we are clicking on test connection the API request we are sending is given below ,

[https://api012.successfactors.eu/odata/v2/PerPerson?%24format=json&customPageSize=1&%24expand=employmentNav%2CemploymentNav%2FuserNav 

It is querying the inactive employee 962 and for that userNav is Null but userprinciple name is in the attribute mapping.

You can see the mapping here and suggest what should we do to set up the connection.

Kindly suggest how can we establish the connection again. Ideally it should skip the inactive employees from the provisioning and allow the password to be updated but that is not happening here.

Answer 3

Hi all,

we are running in a similar issue. Was there a solution for this @Ajit Kumar Chirania?

Thank you,

Sebastian