PI Error calling Microsoft WCF Web Service hosted on IIS

[Former Member]

Hi All,

I am trying to call a Microsoft WCF web service in PI (also tried soapUI) but keep getting certificate error.

I have tested the same service with Microsoft WcfTestClient and everything works..

WCF Service Setup

Service URL: https://hostname/servicename.svc
Security Mode: TransportWithMessageCredential

PI Setup 1 (Should be correct setup)

Communication Channel
Adapter Type: SOAP
Uses Configure Certificate Authentification
Uses Security Profile = Web Service Security
Receiver Agreement
Uses Security Procedure (Request) = Sign
Uses Set Timestamp
Uses Set Expiry Date = 7200
Error: Unable to resolve the '#wsuid-body-5ad10600-3c4a-11e1-c462-005056960025' URI in the signature to compute the digest.

In the SOAP message the references match

<ds:Reference URI="#wsuid-body-5ad10600-3c4a-11e1-c462-005056960025">

<SOAP:Body xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd" wsu:Id="wsuid-body-5ad10600-3c4a-11e1-c462-005056960025">

-

---

Tried the following setups as well

PI Setup 2

Communication Channel
Uses Security Profile = Web Service Security
Receiver Agreement
Uses Security Procedure (Request) = Sign
Uses Set Timestamp
Uses Set Expiry Date = 7200
Error: The security protocol cannot verify the incoming message.

PI Setup 3

Communication Channel
Uses Configure Certificate Authentification
Error: Security processor was unable to find a security header in the message. This might be because the message is an unsecured fault or because there is a binding mismatch between the communicating parties.   This can occur if the service is configured for security and the client is not using security.

Any help would be greatly appreciated

Edited by: Christian Vilhelm Henriksen on Jan 26, 2012 10:13 AM

[Former Member]

Found the following on Microsoft which looks similar to my problem.

http://download.microsoft.com/download/a/2/8/a2807f78-c861-4b66-9b31-9205c3f22252/dotnet35sp1readme....

What it says in short

To resolve this issue:
Do not sign the To header.

How do i do this in PI?

[Former Member]

Hi Christian.

I know this is old, but did you find a way to consume the WCF webservice?. My scenario and error are the same as yours.

I found that PI signs header and body message, so when you consume a WCF WS with additional signed elements you get this error.

Regards,

[rcsegovia]

Hi all,

Any idea about how to do it?

regards,

Roberto.