WSO2 ESB Axis2 Service Error Host Error Hostname for Host

I created an AXIS service that connects to the WSO2 Identity Server and validates the token. When I deploy this axis service to the WSO2 application server, I get the correct answer. Where, when I deploy it to the WSO2 ESB, I get the following error:

org.apache.axis2.AxisFault: The input stream for an incoming message is null. at org.apache.axis2.transport.TransportUtils.createSOAPMessage(TransportUtils.java:93) at org.apache.axis2.transport.TransportUtils.createSOAPMessage(TransportUtils.java:68) at org.apache.axis2.description.OutInAxisOperationClient.handleResponse(OutInAxisOperation.java:346) at org.apache.axis2.description.OutInAxisOperationClient.send(OutInAxisOperation.java:413) at org.apache.axis2.description.OutInAxisOperationClient.executeImpl(OutInAxisOperation.java:224) at org.apache.axis2.client.OperationClient.execute(OperationClient.java:149) at org.wso2.carbon.identity.oauth2.stub.OAuth2TokenValidationServiceStub.validate(OAuth2TokenValidationServiceStub.java:184) at com.xxx4.yyy.security.token.service.TokenValidationService.validateToken(TokenValidationService.java:67) at com.xxx4.yyy.security.token.facade.TokenValidationFacade.validateToken(TokenValidationFacade.java:16) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:606) at org.apache.axis2.rpc.receivers.RPCUtil.invokeServiceClass(RPCUtil.java:212) at org.apache.axis2.rpc.receivers.RPCMessageReceiver.invokeBusinessLogic(RPCMessageReceiver.java:117) at org.apache.axis2.receivers.AbstractInOutMessageReceiver.invokeBusinessLogic(AbstractInOutMessageReceiver.java:40) at org.apache.axis2.receivers.AbstractMessageReceiver.receive(AbstractMessageReceiver.java:110) at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:180) at org.apache.synapse.transport.passthru.ServerWorker.processEntityEnclosingRequest(ServerWorker.java:404) at org.apache.synapse.transport.passthru.ServerWorker.run(ServerWorker.java:184) at org.apache.axis2.transport.base.threads.NativeWorkerPool$1.run(NativeWorkerPool.java:172) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) at java.lang.Thread.run(Thread.java:724) 

[2013-10-03 14: 42: 56,160] ERROR - TargetHandler I / O error: host check failed for host: 172.20.5.110 javax.net.ssl.SSLException: host name check for host: 172.20.5.110 on org. apache.synapse.transport.http.conn.ClientSSLSetupHandler.verify (ClientSSLSetupHandler.java:152) at org.apache.http.nio.reactor.ssl.SSLIOSession.doHandshake (SSLIOSession.java:285) at org.apache.http. nio.reactor.ssl.SSLIOSession.isAppInputReady (SSLIOSession.javahaps72) at org.apache.http.impl.nio.reactor.AbstractIODispatch.inputReady (AbstractIODispatch.java:118) at org.apache.http.impl.nio. reactor.BaseIOReactor.readable (BaseIOReactor.java:160) at org.apache.http.impl.nio.reactor.AbstractIOReactor.processEvent (AbstractIOReactor.javahaps42) at org.apache.http.impl.nio.reactor.AbstractIOReact. processEvents (AbstractIOReactor.javahaps20) at org.apache.http.impl.nio.reactor.AbstractIOReactor.execute (Abstr actIOReactor.java:280) at org.apache.http.impl.nio.reactor.BaseIOReactor.execute (BaseIOReactor.java:106) at org.apache.http.impl.nio.reactor.AbstractMultiworkerIOReactor $ Workerultiorun. Abstract java: 604) in java.lang.Thread.run (Thread.java:724)

+6
source share
2 answers

Set the HostnameVerifier parameter to AllowAll for transportSender in the Axis2 configuration (axis2.xml).

 <transportSender name="https" class="org.apache.synapse.transport.passthru.PassThroughHttpSSLSender"> <!--...--> <!--supports Strict|AllowAll|DefaultAndLocalhost or the default if none specified --> <parameter name="HostnameVerifier">AllowAll</parameter> <!--supports Strict|AllowAll|DefaultAndLocalhost or the default if none specified --> </transportSender> 
+13
source

Adding to Ratha's answer, the following white papers provide a detailed explanation of hostname validation in WSO2 products.

Enabling HostName Validation

+1
source

Source: https://habr.com/ru/post/955172/


All Articles