I would appreciate guidance on how to include custom headers when using OOTB connectors, such as the Guidewire PolicyCenter."

IdentityIQ (IIQ) IIQ Discussion and Questions
1

Hi All,

I would appreciate guidance on how to include custom headers when using OOTB connectors, such as the Guidewire PolicyCenter.

Regards,

Venu

2

Hello Venugopala. I do not see a documented configuration in the OOTB Guidewire PolicyCenter connector for adding arbitrary HTTP headers. The connection settings only expose the Host URL and the authentication parameters (Basic, or OAuth 2.0 with Token URL, Client ID, Client Secret, and Scope). There is no custom-header field.

I would also be cautious about placing a value under connectorAttributes and expecting it to go out as a header. That object is connector-specific configuration, so unless the Guidewire implementation is coded to read that particular attribute and set it on the outbound request, it will not have any effect.

Customizers would not help here either. SaaS Connectivity Customizers only apply to connectors on the supported list, and Guidewire PolicyCenter is not one of them. That mechanism is primarily intended for the Web Services and SCIM 2.0 connectors.

If the integration requires custom headers, the Web Services connector is a documented alternative. Headers there are defined per operation as key/value pairs and sent on the HTTP request, and the header values support expression language if you need to inject a token or a value from the source configuration.

3

i am not able to see anywhere it is mentioned that we can use header attribute, but once u can try like we do in webserice connection







Or if it is constant header then put in base url if that you can achieve ( I doubt it). but lets give a try