Unauthorized call to SCIM client

[smile]

Hi Experts,

I am using the trial account. Configured an SFSF demo system as source and a SCIM compliant other system as target for user provisioning. Connection test works fine for both system. However when the provisioning job runs the calls fail. Looking on the POST requests I have realized that there is no bearer token included in the request. When I do a connection test the bearer token is included there. Might it be a bug in the implementation?

[smile]

Hi Andreya,

I gave it a try and indeed it works, but for me it is still unclear if I use a destination configuration to connect to my target system and that destination has all required information set up(including OAuth) why should I define the same connection details again as additional properties?

[smile]

Hi Andreya,

are you saying that even the target system is configured via a destination and that destination has all the required OAuth configuration, I still have to add the whole configuration again via the properties tab?

[andreyakostov]

Hello Szabolcs Mile,

Please see the documentation page for configuring a SCIM target system. Identity Provisioning has no way of knowing it has to use the OAuth flow if "OAuth2TokenServiceURL" property (it should be highlighted in the linked page) is not configured in your destination or provisioning system properties. Please also note that some of the other properties mentioned in the "Mandatory Properties" table - "User", "Password" and "Authentication" - are also relevant for configuring OAuth authentication to a back-end system.

Regards,
Andreya