Let me add a comment to this from an enterprise architectural viewpoint....
When you define an enterprise architecture one of the absolutely most important tasks is to define domains (meaning a set of system/processes/people that decide over what happens inside their domain) and interfaces. The fundamental idea is to "blackbox" domains from each other - this is the same pattern as defining an API for a system (the best book to demonstrate this is still Fred Brooks
"The Mythical Man Month" from 1975).
An HRfeed is an interface in this sense - when you define such a interface it is important that the "sending" party (here SalesForce) defines the syntax and semantics (meaning - how to interpret a given piece of data) - the latter is very often forgotten with disaster looming...
A classical example is if you have a start date as a data attribute following a yyyymmdd syntax - now - how is that to be interpreted in e.g. IGI ? Most would just say when the day starts it is active which is probably almost correct in most cases - but it could something come from a different timezone or it could that it means something complete different in this specific instance of the sending system e.g. you may get a 1-of error which can cause a lot of problems.
As the example above hopefully shows an out-of-the-box interface of this kind is kind of compromise - either you get some very simple interface (low value) which needs customization to be useful or you may get something that is not always correct.
My advice is that an HRFeed is always negotiated formally as part of your IAM program and documented/maintained as a formal agreement with change control/governance established covering what I outlined above - and then the responsibility for sending data must reside in the sending system (SalesForce) and it is up to the receiving system to adhere to the spefication....
Hope this little lecture in Enterprise Architecture is valuable - I have personally suffered from the impact of not following these principle a couple of times until I finally understood what the underlying problem was :-)
------------------------------
Franz Wolfhagen
IAM Technical Architect for Europe - Certified Consulting IT Specialist
IBM Security Expert Labs
------------------------------
Original Message:
Sent: Fri June 12, 2020 02:51 AM
From: Ranvijay
Subject: IGI SuccessFactor Integration
Dear ,
OOB connector is not available for this Integration . You can find list of connector which is available
https://www.ibm.com/support/pages/ibm-security-identity-adapters-v7x
You can create custom adapter for this integration .
------------------------------
Ranvijay Singh , IAM SME
IBM , Pune
Original Message:
Sent: Fri June 05, 2020 04:41 AM
From: karthikeyan selvarajan
Subject: IGI SuccessFactor Integration
Hi.. Can someone please advise if there is a standard integration approach or connector available for integrating IGI with SuccessFactor as authoritative source ?
------------------------------
karthikeyan selvarajan
------------------------------