on 04-28-2011 10:04 AM
Hello,
we have following scenario:
3rd Party - WS-Adapter - Integration Engine - Webservice Adapter - SAP BI
We have config PI and SAP BI with How To Guide
http://www.google.de/url?sa=t&source=web&cd=4&ved=0CDoQFjAD&url=http%3A%2F %2Fwww.sdn.sap.com%2Firj%2Fscn%2Findex%3Frid%3D%2Flibrary%2Fuuid%2Fb04408cc-f10e-2c10- b5b7-af11026b2393%26overridelayout%3Dtrue&ei=0yW5Tbv8K4zIswbc7KXrAw& usg=AFQjCNEdKnLpCo16LHv4ChjkI2A0jnzTcA]
Now We send a Testmessage from SOAP UI to SAP PI Wbeservice Adapter.
Message:
<soap:Envelope xmlns:v11="http://xmldefs.XXX.com/XXX/XXXService" xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/" xmlns:vwa="http://xmldefs.XXX.com/XXX/XXX/XX" xmlns:wsa="http://www.w3.org/2005/08/addressing">
<soap:Header>
<wsse:Security xmlns:wsse="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd">
<saml:Assertion AssertionID="c17ba406-f8f5-4366-bf99-a6b1fe6bdfa9" ID="c17ba406-f8f5-4366-bf99-a6b1fe6bdfa9" IssueInstant="2010-10-05T09:06:49Z" Issuer="https://ws-xxxx-test.xxx" MajorVersion="1" MinorVersion="1" wsu:Id="c17ba406-f8f5-4366-bf99-a6b1fe6bdfa9" xmlns:saml="urn:oasis:names:tc:SAML:1.0:assertion" xmlns:saml2="urn:oasis:names:tc:SAML:2.0:assertion" xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd">
<saml:Conditions NotBefore="2010-10-05T09:05:49Z" NotOnOrAfter="2010-10-05T09:11:49Z"/>
<saml:AuthenticationStatement AuthenticationInstant="" AuthenticationMethod="">
<saml:Subject>
<saml:NameIdentifier Format="urn:oasis:names:tc:SAML:1.1:nameid-format:unspecified">USERNAME</saml:NameIdentifier>
<saml:SubjectConfirmation>
<saml:ConfirmationMethod>urn:oasis:names:tc:SAML:1.0:cm:sender-vouches</saml:ConfirmationMethod>
</saml:SubjectConfirmation>
</saml:Subject>
</saml:AuthenticationStatement>
</saml:Assertion>
<wsse:SecurityTokenReference wsu:Id="3da617c6-3f0a-457c-b7d8-c78996e1f92b" xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd">
<wsse:Reference URI="#c17ba406-f8f5-4366-bf99-a6b1fe6bdfa9"/>
</wsse:SecurityTokenReference>
<wsse:BinarySecurityToken EncodingType="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-soap-message-security-1.0#Base64Binary" ID="d80a7bde-5645-4fce-bea1-2f7f21828b1f" ValueType="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-x509-token-profile-1.0#X509v3" wsu:Id="d80a7bde-5645-4fce-bea1-2f7f21828b1f" xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd">MIIDLjCCApegAwIBAgIEB8Go3jANBgkqhkiG9w0BAQUFADBtMQswCQYDVQQGEwJERTEWMBQGA1UECBMNTmllZ
GVyc2FjaHNlbjESMBAGA1UEBxMJV29sZnNidXJnMRAwDgYDVQQKEwdLLVNJVC81MSAwHgYDVQQDExdzYi1ub2RlLXRlc
3Qud29iLnZ3LnZ3ZzAeFw0wODA4MjkwOTMwMTlaFw0xODA4MjcwOTMwMTlaMG0xCzAJBgNVBAYTAkRFMRYwFAYDV
QQIEw1OaWVkZXJzYWNoc2VuMRIwEAYDVQQHEwlXb2xmc2J1cmcxEDAOBgNVBAoTB0stU0lULzUxIDAeBgNVBAMTF3Ni
LW5vZGUtdGVzdC53b2IudncudndnMIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQCnkWjCXHgkj00XO0RzqEtesJirTsFe
3GFT8ufT0K7tUHEZzMVePgahAMSKPQk94ej3Z2dVSK0ESq57BtnG54q4VMf1V18TSb9q8HR7NShD9RPBC4QwddcYJ3/awU
+Ul2rJUQI82GWZHv8zwFnmnKEF19pfdi8v76yU2QUvWxewRwIDAQABo4HaMIHXMAwGA1UdEwQFMAMBAf8wHQYDVR0
OBBYEFN9IPjk87yBhCB6DkZFfv4/HyDyfMIGaBgNVHSMEgZIwgY+AFN9IPjk87yBhCB6DkZFfv4
/HyDyfoXGkbzBtMQswCQYDVQQGEwJERTEWMBQGA1UECBMNTmllZGVyc2FjaHNlbjESMBAGA1UEBxMJV29sZnNidXJnMR
AwDgYDVQQKEwdLLVNJVC81MSAwHgYDVQQDExdzYi1ub2RlLXRlc3Qud29iLnZ3LnZ3Z4IEB8Go3jALBgNVHQ8EBAMCAr
wwDQYJKoZIhvcNAQEFBQADgYEAgmDu8ojnvs8A7aeRiLjCShOBV4x5BOTLSqIidIaiD0KUGIeN8A9MUSxgA0EFc8d2nBWt3X
6OvtI0OMJg4+gEB4uspdz0lyPzlx3hE4YBNWk0h0t1zy6K2qlnYi8DfNRAFfQP1BmeZZ1hTMft1hU13BnOCLsv8q1Ya4vhNP6Kqp
w=</wsse:BinarySecurityToken>
<wsse:SecurityTokenReference wsu:Id="1740c802-5d8a-42de-9f66-15312ea33023" xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd">
<wsse:Reference URI="#d80a7bde-5645-4fce-bea1-2f7f21828b1f"/>
</wsse:SecurityTokenReference>
<ds:Signature Id="63543d0c-84a8-4f86-ac37-8c5773a73650" xmlns:ds="http://www.w3.org/2000/09/xmldsig#">
<ds:SignedInfo xmlns:saml="urn:oasis:names:tc:SAML:1.0:assertion">
...
</ds:SignedInfo>
<ds:SignatureValue>NV846EMLD8YPpnWeT48z0Vz7yhXjZFFrp3rvUXA0Yfsbi4mr6ArNTgPUt1Z9MzTvvovXXdCcHZz7y
fU6lk6eIbL91eKw4oWZFlRCH1IMk3tLjyJsdFhNmAycYxDao4p8Zg1JQEyd8UgGYu8EJnfMV9jcaYr5piNdW6Yn4=
</ds:SignatureValue>
<ds:KeyInfo>
<wsse:SecurityTokenReference>
<wsse:Reference URI="#d80a7bde-5645-4fce-bea1-2f7f21828b1f"/>
</wsse:SecurityTokenReference>
</ds:KeyInfo>
</ds:Signature>
</wsse:Security>
</soap:Header>
<soap:Body>
...
</soap:Body>
</soap:Envelope>
As Response we get:
...
<soap-env:Body>
<soap-env:Fault>
<faultcode>soap-env:Server</faultcode>
<faultstring xml:lang="en">CX_WS_SECURITY_FAULT:Invalid XML signature</faultstring>
<detail>
<ns:SystemFault xmlns:ns="http://www.sap.com/webas/710/soap/runtime/abap/fault/system/">
<Host>undefined</Host>
<Component>APPL</Component>
<ChainedException>
<Exception_Name>CX_SOAP_CORE</Exception_Name>
<Exception_Text>CX_WS_SECURITY_FAULT:Invalid XML signature</Exception_Text>
</ChainedException>
<ChainedException>
<Exception_Name>CX_WS_SECURITY_FAULT</Exception_Name>
<Exception_Text>Invalid XML signature</Exception_Text>
</ChainedException>
...
How to resolve this error?
Thanks and regards
Martin
I suggest the next steps:
1) Review the URL
2) See if SoapUI are using "https" in the request, change it by "http".
check with your basis team if you need to use https, in that case you have to install a
certificate in your WS client
3) Check if the port of the URL of the request is correct, by default the port is 50000
(check it whith your basis team)
2) you need the next rol assigned to the user of PI that you use to consume the WS : SAP_BC_WEBSERVICE_CONSUMER
Regards,
Luis Manuel
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Martin,
Follow SAP note 1529353 maybe can solve your problem..
Thx
Glenn
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
84 | |
25 | |
12 | |
9 | |
7 | |
6 | |
5 | |
5 | |
4 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.