I am currently working on integrating SAP Fieldglass with SailPoint IdentityNow and I wanted to start a discussion around the available out-of-the-box configurations for provisioning. My main focus is to understand how provisioning workflows like user creation, updates, and terminations can be managed through SailPoint IdentityNow when connecting to Fieldglass. Since Fieldglass exposes REST-based APIs, I am evaluating whether a custom REST connector is the preferred approach or if there is a native integration option available from SailPoint. Another important point I am looking into is the authentication mechanism. I would like to know whether most implementations rely on OAuth2, basic authentication, or any other API token-based approach when establishing communication with Fieldglass services.
I am also curious about how the community is handling the contractor lifecycle events in Fieldglass and mapping those effectively in IdentityNow for automated provisioning and deprovisioning. Additionally, if anyone has experience with importing position data or job requisitions from Fieldglass services into IdentityNow for use in access decisions or role modeling, I would be interested in hearing how that process was implemented. Insights into approval workflow design, logging strategies for audit compliance, and real-world provisioning rules would also be extremely valuable.
If anyone has gone through a similar integration or has best practices to share related to SAP Fieldglass and SailPoint IdentityNow, I would appreciate your input.