Webservice connector in iiq

IdentityIQ (IIQ) IIQ Discussion and Questions
,
1

I want to learn about the Web Service Connector in SailPoint IdentityIQ.

I have a few questions:

  • Where can I download the Web Service Connector?

  • What is the folder structure of the Web Service Connector?

  • What are the files we need to develop or configure?

  • How can we implement and test it in IdentityIQ?

  • Do we need to develop everything from scratch, or are there any predefined templates or configurations available?

I would appreciate it if anyone could share documentation, examples, or implementation guidance.

2

Hi Ramesh,

You should just read he Webservices connector documentation first.

Regards,

Pradeep

3

Please share the Webservices connector documentation.

4

The Web Services connector is bundled with IIQ, nothing separate to download. Once deployed, go to Applications > Application Definition > Add New Application and select Web Services as the application type.

There’s no folder structure to set up. Everything lives in the application definition: base URL, auth method (Basic, OAuth2, API Token, or no auth), object types, schema, and operation configs. The connector jars are in WEB-INF/lib-connectors but you don’t touch those.

What you’ll actually work with:

  • Application XML (exported via debug or iiq console) for operation configs, request/response mappings, and attribute definitions

  • Before/After Operation Rules only when you need to manipulate payloads, handle non-standard responses, or persist values in connectorStateMap

Build order matters: define your schema, get aggregation working cleanly, and validate the underlying API calls in Postman first. Add provisioning operations (Create, Update, Enable/Disable, entitlements) only after aggregation is stable.

Official docs matched to your IIQ version and patch: Integrating SailPoint with Web Services. Connector behavior and supported options vary across IIQ releases, so version matters. The Supported Connectors for IdentityIQ page on Compass has the correct PDF for your specific version.

If the target system is behind your firewall, this is the VA-based connector, not the SaaS Web Services connector. The Compass connector directory clarifies the distinction.

5
6

All connectors are available here