Error while signing in SOAP receiver channel

Hi,
I have a Source PI which is sending a XML message to a target PI through SOAP adapter. Its a secure commnication. I am using message level encryption and signing on the source receiver agreement and message level decryption and validation on target sender agreement. The message is failing in the SOAP receiver cahnnel on source PI with the below error message. Also, I am using a certificate which is signed by Verisign and its valid for two years. I have checked the validity, it has not expired yet.
It works fine if the certificate is signed by SAP(that is, test certificate which is valid for 8 weeks).
Error Message
Message processing failed. Cause: com.sap.engine.interfaces.messaging.api.exception.MessagingException: SOAP: response message contains an error XIServer/UNKNOWN/ADAPTER.JAVA_EXCEPTION - com.sap.engine.interfaces.messaging.api.exception.MessagingException: com.sap.aii.security.lib.exception.SecurityException: SecurityException in method: verify( Message, byte[], CPALookupObject ). Message: SecurityException in method: verify( Message, byte[], CPALookupObject ). WSSEThread-Exception: SecurityException in method: run(). Message: [_policy0230] The part /soap:Envelope/soap:Body was required to be signed by the policy with the transformations [], but the signature was not accepted. (Info: number of valid signatures: 1, number of accepted signer certificates: 0.).. To-String: com.sap.security.core.policy.exceptions.VerifyException: [_policy0230] The part /soap:Envelope/soap:Body was required to be signed by the policy with the transformations [], but the signature was not accepted. (Info: number of valid signatures: 1, number of accepted signer certificates: 0.).; To-String: com.sap.aii.security.lib.exception.SecurityException: SecurityException in method: run(). Message: [_policy0230] The part /soap:Envelope/soap:Body was required to be signed by the policy with the transformations [], but the signature was not accepted. (Info: number of valid signatures: 1, number of accepted signer certificates: 0.).. To-String: com.sap.security.core.policy.exceptions.VerifyException: [_policy0230] The part /soap:Envelope/soap:Body was required to be signed by the policy with the transformations [], but the signature was not accepted. (Info: number of valid signatures: 1, number of accepted signer certificates: 0.).. To-String: com.sap.aii.security.lib.exception.SecurityException: SecurityException in method: verify( Message, byte[], CPALookupObject ). WSSEThread-Exception: SecurityException in method: run(). Message: [_policy0230] The part /soap:Envelope/soap:Body was required to be signed by the policy with the transformations [], but the signature was not accepted. (Info: number of valid signatures: 1, number of accepted signer certificates: 0.).. To-String: com.sap.security.core.policy.exceptions.VerifyException: [_policy0230] The part /soap:Envelope/soap:Body was required to be signed by the policy with the transformations [], but the signature was not accepted. (Info: number of valid signatures: 1, number of accepted signer certificates: 0.).; To-String: com.sap.aii.security.lib.exception.SecurityException: SecurityException in method: run(). Message: [_policy0230] The part /soap:Envelope/soap:Body was required to be signed by the policy with the transformations [], but the signature was not accepted. (Info: number of valid signatures: 1, number of accepted signer certificates: 0.).. To-String: com.sap.security.core.policy.exceptions.VerifyException: [_policy0230] The part /soap:Envelope/soap:Body was required to be signed by the policy with the transformations [], but the signature was not accepted. (Info: number of valid signatures: 1, number of accepted signer certificates: 0.). at com.sap.aii.adapter.soap.ejb.XISOAPAdapterBean.process(XISOAPAdapterBean.java:996) at sun.reflect.GeneratedMethodAccessor546_10002.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at com.sap.engine.services.ejb3.runtime.impl.RequestInvocationContext.proceedFinal(RequestInvocationContext.java:43) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:166) at com.sap.engine.services.ejb3.runtime.impl.Interceptors_StatesTransition.invoke(Interceptors_StatesTransition.java:19) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177) at com.sap.engine.services.ejb3.runtime.impl.Interceptors_Resource.invoke(Interceptors_Resource.java:71) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177) at com.sap.engine.services.ejb3.runtime.impl.Interceptors_Transaction.doWorkWithAttribute(Interceptors_Transaction.java:38) at com.sap.engine.services.ejb3.runtime.impl.Interceptors_Transaction.invoke(Interceptors_Transaction.java:22) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:189) at com.sap.engine.services.ejb3.runtime.impl.Interceptors_StatelessInstanceGetter.invoke(Interceptors_StatelessInstanceGetter.java:16) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177) at com.sap.engine.services.ejb3.runtime.impl.Interceptors_SecurityCheck.invoke(Interceptors_SecurityCheck.java:21) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177) at com.sap.engine.services.ejb3.runtime.impl.Interceptors_ExceptionTracer.invoke(Interceptors_ExceptionTracer.java:16) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177) at com.sap.engine.services.ejb3.runtime.impl.DefaultInvocationChainsManager.startChain(DefaultInvocationChainsManager.java:133) at com.sap.engine.services.ejb3.runtime.impl.DefaultEJBProxyInvocationHandler.invoke(DefaultEJBProxyInvocationHandler.java:164) at $Proxy2684_10002.process(Unknown Source) at com.sap.aii.af.app.mp.ejb.ModuleProcessorBean.process(ModuleProcessorBean.java:275) at

Hi,
as per the error message is:
"... The part /soap:Envelope/soap:Body was required to be signed by the policy with the transformations [], but the signature was not accepted. (Info: number of valid signatures: 1, number of accepted signer certificates: 0.) ..."
I guess the cert. setup either on your side or the other system's side is not fully correct. Check whether all cert., priv keys and public keys are exchanged propperly and setup as trusted certs.
Regards,
Kai
Edited by: Kai Lerch-Baier on Jul 9, 2009 1:24 PM

Similar Messages

Error in SOAP receiver channel in Synchronous Proxy to SOAP scenario

Hi all,
We are experiencing an issue with a synchronous Proxy to SOAP scenario. Getting below error message in the SOAP receiver communication channel for the response message.
SOAP: Response message contains an errorXIAdapter/HTTP/ADAPTER.HTTP_EXCEPTION - HTTP 500 Internal Server Error
Returning to application. Exception: com.sap.engine.interfaces.messaging.api.exception.MessagingException: Error encountered while executing mapping: com.sap.aii.af.service.mapping.MappingException: com.sap.aii.utilxi.misc.api.ResourceException: Could not determine mapping steps for message 1364b76e-ecbf-11e4-85f4-000023acfde6.
We are running PI 7.4.
Any help is appreciated.
Thanks,
Pushpa

Hi,
Seems the Receiver Webservice is not reachable. Did you try to test it using SOAP UI tool.
1. Test a fresh message from local SOAP UI tool.
2. Pick 3rd party WSDL file and Import in SOAP UI tool.
3. Put some dummy data for mandatory fields
4. Trigger it msg and ckh if you get successful / response msg.
5. Check if firewall is open and that URL is not blocked.
Hope it helps
Regards,
Azhar

Error in SOAP Receiver channel

Hi,
We are working on IDOC to SOAP Scenario (Connecting to third party).
We have configured the SOAP Receiver channel with the Target URL and teh corresponding SOAP Action.
But the SOAP Receiver channel gives the error while processing and sends back the following error message in log :
"Delivery of the message to the application using connection SOAP_http://sap.com/xi/XI/System failed, due to: com.sap.aii.af.ra.ms.api.RecoverableException: SOAP: response message contains an error XIAdapter/PARSING/ADAPTER.SOAP_EXCEPTION - soap fault: Server was unable to process request. ---> Value cannot be null. Parameter name: s."
Payload seems to look fine in XI and SAP.
Any help on this ?
Thanks and regards,
Vikas

Hi Vikas,
Copy the payload from SXMB_MONI after mapping and check with SOAPGUI or Altova, if it working fine then your payload is good. You can use the WSDL to ganarate and send independent soap request from these tools.
Besides this IDOC is Asyc, you need to use RequestResponseBean and ResponseOneWayBean to get the response from SOAP. Check the following and try to simulate it.
https://wiki.sdn.sap.com/wiki/display/XI/File-RFC-File%28Without+BPM%29
Server was unable to process request. ---> Value cannot be null. Parameter name: s."
The error specifies that the request has null value, check the parameter specified in the error message and make sure that is not null while you are sending the request.
Regards,
Prasanna

SOAP Receiver Channel error

Dear PI and SOAP experts:
I have been having trouble getting a SOAP Receiver channel working for a webservice. I get the following error in the SOAP receiver channel:
SOAP: response message contains an error XIAdapter/PARSING/ADAPTER.SOAP_EXCEPTION - soap fault: content-type of the request should be text/xml
I also forced the content-type as text/xml;charset=utf-8 from PI by using the MessageTransformBean as a module in the SOAP Receiver channel, but still getting the same response.
When I called the same w/s using XMLSpy and SOAPUI, it works fine and I get a positive response. So there is no problem with the webservice.
I also tried calling a different webservice from PI and that works fine too. So there is no problem with outbound communication with PI and the SOAP receiver channel either.
But whenever I send the request from PI to the first webservice it gives me the above error.
Thank you.
Param.

Hi Param,
Also, please do have a look at the following link which could be of help to you.
https://wiki.sdn.sap.com/wiki/display/XI/SOAPMessagesin+XI
Best Regards

Error in SOAP receiver channel: java.io.IOException: invalid http response:

Hi experts,
I have a IDOC to SOAP scenario where SOAP receiver channel is sending data to web service. In the receiver channel I am getting error as below. Kindly help me to resolve this issue. Thanks.
"Message processing failed. Cause: com.sap.engine.interfaces.messaging.api.exception.MessagingException: java.io.IOException: invalid http response: null"

Did you check this?
http://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/40611dd6-e66e-2910-f383-e80fb44f9cd4
Regards
Pothana

"Unauthorized" error for SOAP receiver channel

Hi all,
I have a scenario in which I am calling a .NET web service from a UDF in which the XML payload is constructed manually. I have configured a SOAP receiver channel. Also, since the web service needs certificate authentication, I have checked the corresponding parameter in the SOAP channel and selected appropriate client certificate.
When I execute the mapping, I get the following error -
com.sap.aii.mapping.lookup.LookupException: Exception during processing the payload.Problem when calling an adapter by using communication channel SOAP_RCV_IMWS_Change (Party: , Service: IMWS, Object ID: dda07d364ca73d4ab9e89e562a971b36) XI AF API call failed. Module exception: 'com.sap.aii.af.ra.ms.api.RecoverableException: invalid content type for SOAP: TEXT/HTML; HTTP 401 Unauthorized: java.io.IOException: invalid content type for SOAP: TEXT/HTML; HTTP 401 Unauthorized'. Cause Exception: 'invalid content type for SOAP: TEXT/HTML; HTTP 401 Unauthorized'.
Is this related to error in certificate authentication process, OR wrongly formed XML payload OR anything else ?
Regards,
Shankar

No. I didn't provide any login info. The web service doesn't specify username login requirement. Instead, it needs client certificate for authentication, which I provided in SOAP receiver channel.
I am testing the web service by executing the message mapping. The web service was executed successfully from its 'Test Page' like for SAP web services we have web service navigator. So it runs ok from that test page, but gives error when called from UDF.
Regards,
Shankar

Error while signing data-Private key or certificate of signer not available

Hello All,
I am new to PI. I am currently stuck with an issue. The scenario is as explained below.
We need to check for the service availability before processing the data. So, we test for the RFC connection first from the ECC system. During this process, we access the digital certificate stored in the PI system so that it can be validated and allowed to consume this intended service.
Error :
When we trigger the RFC test from the ECC system, we get an error stating ' Error while signing data - Private key or certificate of signer not available '. But when we test the same functionality within PI system(Locally), we does not encounter any such error. The certificate is maintained and it appears fine.
The communication channels are stored with logon credentials.
Can anyone please help me with this error or provide your valuable inputs. Thanks in advance.
Regards,
Shivkumar

Hello,
When we trigger the RFC test from the ECC system, we get an error stating ' Error while signing data - Private key or certificate of signer not available '.
This should be normal behavior since the certificates are not installed in ECC SSL folders of Strust. Why not just install the certificates in the ECC system, perform an ICM restart and do a retest? After all, the certificates would both be the same in PI and ECC.
Hope this helps,
Mark

Error while signing in. No prompt for Master Password.

Firefox 3.6.15 (Mozilla/5.0 (Windows; U; Windows NT 5.1; sv-SE; rv:1.9.2.15) Gecko/20110303 )
Firefox sync 1.7
Sync NEVER works automatically. In a new FF session it always reports "Error While Signing In". If I try to connect manually I must go through the set-up dialogue and enter my Master Password etc and then it works (during that session).
I have a Master Password defined.
Sync doesn't prompt for that before trying to connect. So the connection fails and sync concludes that a set-up must be performed.
Useless extension in current state.

Hi,
as per the error message is:
"... The part /soap:Envelope/soap:Body was required to be signed by the policy with the transformations [], but the signature was not accepted. (Info: number of valid signatures: 1, number of accepted signer certificates: 0.) ..."
I guess the cert. setup either on your side or the other system's side is not fully correct. Check whether all cert., priv keys and public keys are exchanged propperly and setup as trusted certs.
Regards,
Kai
Edited by: Kai Lerch-Baier on Jul 9, 2009 1:24 PM

The test encountered an error while signing in to Outlook Web App. HTTP code: 200

Infrastructure: Exchange 2010 SP3 RU2 environment on 17 servers worldwide with CAS, MB, HUB and UM roles. Server 2008 R2 VM's on Hyper-V 2008 R2.
Trying to run the following command to test OWA connectivity on a server in the same Active Directory domain but in a different AD site:
Get-ClientAccessServer -Identity Server1 | test-owaconnectivity -AllowUnsecureAccess -TrustAnySSLCertificate
I get the reponse:
WARNING: [11:04:51.276] : An Outlook Web App page wasn't received.
WARNING: [11:04:51.276] : The test encountered an error while signing in to Outlook Web App.
HTTP code: 200
WARNING: [11:04:51.276] : Test failed for URL 'https://server1.domain.com/owa/'.
ClientAccessServer        MailboxServer            URL
Scenario       Result       Latency          Error
Server1.domain.com      Server2.domain.com  https://server1.domain.com/owa  Logon           Failure
The test encountered an error while signing in to Outlook Web App. HTTP code: 200
This is the same error message received from SCOM on its tests also.
I have created a test account on all 17 servers using ./new-TestCasConnectivityUser and ensured their mailboxes reside on the correct server in the correct database.
All internal servers are set for OWA and ECP for Windows Authentication. Only public facing CAS servers are set to Forms based. That said, have checked the 'Microsoft Exchange Forms-Based Authentication service' is running on both Server1 and Server2 as
are all Exchange services except 'Microsoft Exchange IMAP4' (not used) or 'Microsoft Exchange POP3' (not used).
However, if I run this command:
test-owaconnectivity -AllowUnsecureAccess -TrustAnySSLCertificate -URL
https://server1.domain.com/owa
I get the following success after I have entered my correct credentials:
Windows PowerShell Credential Request : cmdlet Test-OwaConnectivity at command pipeline position 1
Warning: This credential is being requested by a script or application on the Server2.domain.com remote computer.
Enter your credentials only if you trust the remote computer and the application or script requesting it.
Supply values for the following parameters:
MailboxCredential
ClientAccessServer MailboxServer URL
Scenario              Result      Latency    Error
(ms)
                                                        https://server1.domain.com/owa
Logon                 Success    6282.13
So if I login with my domain username, it works and logs in. If the script runs using the 'extest....' user account created by the above ./new-TestCasConnectivityUser.ps1 , it does not work.
Has anyone got any ideas please? I know its not the network as it works under my username, I know all fo the services required are running as it works under my username. There are no entries at all in the receiving server's error logs for Application, System,
Exchange or Powershell at all.
Any help greatly appreciated.
Danny

Did you read this? http://support.microsoft.com/kb/2277649/en-us
Did you run Test-MapiConnectivity? If not, can you run and post results?
HossFly, Exchange Administrator

Unknown error while signing in

Firefox 3.6.13 + Sync 1.7
Entered username and password okay.
Received the sync key.
While trying to connect I get an "unknown error" displayed in red in the preference dialogue,
or
"Error While Signing In" when I hit the Connect button at lower right corner of Firefox, if I hit that button I get "Sync encountered an error while connecting: Unknown error. Please try again."
This is from a home wireless broadband account, there are not any firewalls in place, and using NAT.
Thanks.

I noticed this error in the JS console:
Error: uncaught exception: [Exception... "Component returned failure code: 0x80520012 (NS_ERROR_FILE_NOT_FOUND) [nsIXPCComponents_Utils.import]" nsresult: "0x80520012 (NS_ERROR_FILE_NOT_FOUND)" location: "JS frame :: file:///home/XXX/.mozilla/firefox/9da8ohi4.default/extensions/%7B340c2bbc-ce74-4362-90b5-7c26312808ef%7D/crypto-modules/WeaveCrypto.js :: <TOP_LEVEL> :: line 45" data: no]

Issue in Dynamic configuration in SOAP receiver channel

Hi All,
My scenario is file to SOAP. At receiver side I want to generate URL dynamically.
To proceed step by step, I started with passing a constant URL to Dynamic configuration UDF.
mapping:
Dynamic conf. UDF
Channel Configuration:
From testing, I found that channel always takes the url given in Target URL field and dynamic URL in TserverLocation is been ignored by the channel.
That is dynamic configuration is not working completely.
I went through a lot of blogs and also tried a lot of trial and error methods, but none helped. Every thing I configured looks perfect for me, but still not working. I don't understand where I went wrong. Please help me.

Hi Experts,
I am facing similar issue,
URL --> UDF --> @dynamicvariable
I have created a variable underparent node eg: DESADV-->dynamicvariable
passed complete URL to UDF, below is the UDF
& configured SOAP Receiver Channel as well. This is IDOC to IDOC scenario, using IDOC_AAE on sender side and SOAP on receiver in single stack.
--> Checked ASMA
--> Checked Variable Transport Binding and given "TServerLocation" without quotes in XHeaderName1
--> Target URL: http://
But when I am running this interface, nothing is coming in Dynamic configuration.
Ref: Message Log:
MM and OM is also perfect in ESR.
Any suggestions? Please advice.
Regards
Singh

SOAP Receiver Channel 2 nodes inactive in Production system

Hi All,
We are facing an issue with the SOAP receiver channels in production system. There are 4 nodes which can be seen in the communication channel monitoring and out of which 2 have the status as inactive and the short log says "inactive or never used".
But the same nodes are active on the sender SOAP channel and all other channels.We have also checked the Status of the SOAP service that is also set to active.
Now when the server (App server5 in our case) is switched off, which has the 2 active nodes, the messages are not processed since the nodes on the other server are inactive.
Request you to please help us out in finding out why the nodes are in inactive status only for SOAP receiver channels. Do we need to change any settings at the adapter engine level.
Thank you.
Regards,
Sarvesh Desai
Edited by: Sarvesh Nispat Desai on Aug 25, 2010 5:25 PM

There is an error in reporting the status of SOAP channels. This error has already been fixed by SAP and is available as a fix in higher releases (PI 7.10 and above, latest SPs) .
The status "inactive or never used" is shown in channel monitoring at the following two times:
1. After creating a new SOAP channel (sender/receiver) till this channel processes any new message.
2. After the PI system is restarted, all the SOAP channels show this status, though they are ready to handle any incoming/outgoing messages. The channels continue to display this status till they process any new message.
In both these situations, the SOAP Channel can handle/process messages successfully. So, kindly ignore this channel status ("inactive or never used") reporting error in channel monitoring. This will not at all hamper the normal functioning of the SOAP channels.
Hope this answers your query.

Webservice secuirty in SOAP receiver channel in PI 7.1

One of my vendor published a web service which I imported in PI , but he expcets PI to send webservice secuirty with usertoken, so that they can authenticate & authorize.
How can we implement webservice secuirty with usertoken & password in PI 7.1 on SOAP receiver channel.
Please let me know your thoughts.

I mean while message is going out from XI it should pass username & password as a part of SOAP Header. like below
which I beleive we can call it is as web service security with usertoken
<SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/" xmlns:SOAP-ENC="http://schemas.xmlsoap.org/soap/encoding/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" >
<SOAP-ENV:Header xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/" >
<wsse:Security soapenv:mustUnderstand="1" xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:wsse="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd" >
<wsse:UsernameToken>
<wsse:Username>abcd1234</wsse:Username>
<wsse:Password type="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-username-token-profile-1.0#PasswordText" >abcd2009</wsse:Password>
</wsse:UsernameToken>
</wsse:Security>
</SOAP-ENV:Header>
<SOAP-ENV:Body>

Time out - SOAP Receiver Channel

Hi All,
My Scenario is Database --> PI (7.1) --> SOAP (synchronous) .
The WebService is taking around 15 mins for giving the Response back to PI SOAP Adapter.But, because of Time Out at the PI SOAP Receiver adapter , I am getting "INBOUND EXPIRED" error.
I referred the following links and tried to Increase the time out value in the SOAP Receiver communication channel - Module Parameters.But, this is not working.
1. Note : 856597
2.XMBWS.Timeout in soap receiver channel not working
Can you please let me know if there any possible approach to increase the time out for SOAP Receiver Channel ?
Thanks and regards,
Midhusha.

Hi,
Have a look to below discussions
XMBWS.Timeout in soap receiver channel not working
SOAP Receiver communication channel Error
Timeouts in SOAP Receiver Adapter
Regards
Aashish Sinha

User role for user authentication in a SOAP receiver channel

Hi,
What is the role required for a user in a SOAP receiver channel. This user is specified in the User Authentication while configuring the channel.

Hi,
User Authentication is not mandatory but If your Web service requires logon data, select the Configure User Authentication checkbox and fill in the corresponding fields.
If the Web service is outside your system landscape and you need to address a proxy
server, select the Configure Proxy checkbox.
The sender SOAP adapter does not require a SOAP action, but you always have
to apply logon data when using the SOAP adapter. In the central adapter engine
you can use a service user such as xiappluser; in a non-central adapter
engine or a PCK you must use one of the user names assigned to security role
xi_adapter_soap_message for component XISOAPAdapter.
Regards,
Divya

Error while signing in SOAP receiver channel

Similar Messages

Maybe you are looking for