Receiver SOAP Adapter CC monitor error

[prasanna_shanmugasundaram]

Hi,

Im getting the following error in the CC monitor for the soap adapter. We are using PI7.1.

Pls let me know what could be the possible error. We are using encryption and signing in the receiver agreement. The encryption key and the TrustedCA are vaild ones. Is this error related to it. Pls help. I have done CPA cache refresh (delta and full), deleted the communication channel and receiver agreement and created them again and again 1...n number of times. Pls advice.

Message processing started

request entering

error in response

Message processing failed. Cause: com.sap.engine.interfaces.messaging.api.exception.MessagingException: SOAP: response message contains an error XIServer/UNKNOWN/ADAPTER.JAVA_EXCEPTION - java.security.PrivilegedActionException: com.sap.aii.af.security.impl.exception.MessageSecurityException: MessageSecurityException in Method: VerifyMessageLevelSecurity.run(). AccessControlException. Please check that your Code has the XiSecurityRuntimePermission.Context: com.sap.aii.af.security.impl.exception.MessageSecurityException: Exception in Method: verify( Message, byte[], CPALookupObject ). General exception, no further informations. Message: MessageSecurityContext in Method: verify( Message, byte[], CPALookupObject ). VerifyThread Message: VerifyException in Method: run(). Key: 0150; To-String: com.sap.aii.af.security.impl.exception.MessageSecurityException: VerifyException in Method: run(). Key: 0150. To-String: com.sap.aii.af.security.impl.exception.MessageSecurityException: MessageSecurityContext in Method: verify( Message, byte[], CPALookupObject ). VerifyThread Message: VerifyException in Method: run(). Key: 0150; To-String: com.sap.aii.af.security.impl.exception.MessageSecurityException: VerifyException in Method: run(). Key: 0150. at java.security.AccessController.doPrivileged(AccessController.java:250) at com.sap.aii.af.mp.soap.ejb.WSSecurityExtension.doValidate(WSSecurityExtension.java:231) at com.sap.aii.af.mp.soap.ejb.WSSecurityExtension.invokeOnRequest(WSSecurityExtension.java:119) at com.sap.aii.messaging.srt.ExtensionBubble.onMessage(ExtensionBubble.java:50) at com.sap.aii.af.mp.soap.ejb.XISOAPAdapterBean.process(XISOAPAdapterBean.java:958) at com.sap.aii.af.mp.module.ModuleLocalLocalObjectImpl0_3.process(ModuleLocalLocalObjectImpl0_3.java:103) at com.sap.aii.af.mp.ejb.ModuleProcessorBean.process(ModuleProcessorBean.java:292) at com.sap.aii.af.mp.processor.ModuleProcessorLocalLocalObjectImpl0_0.process(ModuleProcessorLocalLocalObjectImpl0_0.java:103) at com.sap.aii.af.mp.soap.web.MessageServlet.callModuleProcessor(MessageServlet.java:183) at com.sap.aii.af.mp.soap.web.MessageServlet.doPost(MessageServlet.java:512) at javax.servlet.http.HttpServlet.service(HttpServlet.java:760) at javax.servlet.http.HttpServlet.service(HttpServlet.java:853) at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:401) at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:266) at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:386) at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:364) at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:1039) at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:265) at com.sap.engine.services.httpserver.server.Client.handle(Client.java:95) at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:175) at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33) at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41) at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37) at java.security.AccessController.doPrivileged(AccessController.java:219) at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:104) at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:176) Caused by: com.sap.aii.af.security.impl.exception.MessageSecurityException: MessageSecurityException in Method: VerifyMessageLevelSecurity.run(). AccessControlException. Please check that your Code has the XiSecurityRuntimePermission.Context: com.sap.aii.af.security.impl.exception.MessageSecurityException: Exception in Method: verify( Message, byte[], CPALookupObject ). General exception, no further informations. Message: MessageSecurityContext in Method: verify( Message, byte[], CPALookupObject ). VerifyThread Message: VerifyException in Method: run(). Key: 0150; To-String: com.sap.aii.af.security.impl.exception.MessageSecurityException: VerifyException in Method: run(). Key: 0150. To-String: com.sap.aii.af.security.impl.exception.MessageSecurityException: MessageSecurityContext in Method: verify( Message, byte[], CPALookupObject ). VerifyThread Message: VerifyException in Method: run(). Key: 0150; To-String: com.sap.aii.af.security.impl.exception.MessageSecurityException: VerifyException in Method: run(). Key: 0150. at com.sap.aii.af.mp.soap.ejb.WSSecurityExtension$VerifyMessageLevelSecurity.run(WSSecurityExtension.java:523) at java.security.AccessController.doPrivileged(AccessController.java:246) ... 25 more

Thanks

Prasanna

[prasanna_shanmugasundaram]

Thanks

Prasanna

[former_member4985]

Hi Prasanna,

The problem seems that the certificate chain is not in correct

order. Basically the server certificate chain should be in order

Own->Intermedite->Root. To explain in detail, if your server certificate

is A which is issued by an intermediate CA B and then B's certificate is

issued by the C which is the root CA (having a self signed certificate).

Then your certificate chain contains 3 elements A->B->C. So you need to

have the right order of certificate in the chain. If the order is B

first followed by A followed by C, then the IAIK library used by PI

cannot verify the server as trusted. Please generate the certificate in

the right order and then import this certificate in the TrustedCA

keystore view and try again.

With regards,

Caio Cagnani

[prasanna_shanmugasundaram]

Hi Thanks!! The problem was with my business partner. Their certificate was not installed properly or their root certificate has expired.

Thanks

Prasanna

[former_member200962]

Please check that your Code has the XiSecurityRuntimePermission.

Check point 6 of this help section:

http://help.sap.com/saphelp_nw04/helpdata/en/43/a52f2e63161bbfe10000000a1553f7/frameset.htm

Regards,

Abhishek.

[stefan_grube]

Please check that your Code has the XiSecurityRuntimePermission.

There was a similar thread recently:

It seems that your certificates are not vaild.

[prasanna_shanmugasundaram]

Hi Abhi,

Thanks for your reply, as you know the VisualAdmin is quite different (or not visualadmint) in PI7.1

Can you pls suggest where to see there permissions in PI 7.1

Thanks

Prasanna

[prasanna_shanmugasundaram]

Thanks Stefan,

Just before you replied, I went thru the same link . My understand from the thread is that the certificate was error on the customer's side. So should I ask my business partnet to check if they have installed proper certificates or is the problem on my side. In case of error on my side how to check it. I see the private key and the Trusted CA are valid in my key store. We are on PI7.1 Pls advice.

Thanks

Prasanna

[stefan_grube]

To be honest: I have no idea. I do not understand much about certificates.

All I know that this error message is misleading.

You need not give any extra permission for the SOAP adapter.

[Former Member]

Hi,

Report this issue to your receiving partner. There's nothing wrong at your end. If they update the certificate / keys, then you have to update those in PI as well.

Regards,

Neetesh