I am exploring the integration of SailPoint with Guidewire ClaimCenter, particularly around enhancing user account provisioning processes. Before starting, I wanted to reach out to the community to gather some insights from those who have already embarked on this journey.
Here are a few questions I have:
1: Did you need to bring in external developers, or was it manageable with in-house resources?
2: How much time did the integration process take, and was it a significant investment in terms of cost? Were there any unexpected challenges that extended the timeline or added to the cost?
3: Is there anything you wish you had known before starting the integration? Any tips or best practices that could help me?
4: What use cases were you able to successfully address by connecting SailPoint with Guidewire ClaimCenter? Did the integration meet your expectations?
5: If you worked with custom fields within Guidewire ClaimCenter, how was your experience integrating these with SailPoint? Were there any complexities or challenges in mapping these fields, and how did you overcome them?
Iām particularly interested in hearing about real-world experiences, so any details you can share to any of these questions would be greatly appreciated!
@JMC3060
We have done Cloud Guidewire Centers integrations with ISC using webservice connectors, OOTB connector came out recently still OOTB connectors has limitations like currently only supports 2 entitlement types (groups and roles) we had 4 entitlement types, so web service connector was our only option.
Webservice connector would require developer with Java + Sailpoint API knowledge. OOTB connector might not require if you have straight forward usecase.
2-3 weeks of effort if going via webservice connector route. Complex usecase and customization might extend timelines.
Platform (SaaS or Onprem), Guidewire center versions, requirements for user management, availability of GW Center developer for customization.
Using web service connector
Create/Modify/Disable account
Add/Remove entitlement (roles, groups etc)
From webservice connector implementation perspective.
GW Center OOTB API has some basic user attributes, if usecase is to get more details when we either do aggregation or provisioning then GW teams need to customize OOTB API to add those attributes so the ISC can the ingest it during aggregation or provisioning. For example: email address is not available as part of GW OOTB API.