I am getting an error message that hessian has an issue with active sync Connection. What does hessian in an SSL-Certificate Context? Is it used for handshake?
Hessian is not an SSL concept. It is a web service protocol. You did not provide enough info, but my guess is your server certificate can't be validated on the client when connecting to the service.
Related
HTTP Request node connecting to a third party REST API, which is hosted on AWS intermittently throwing "A timeout error occurred whilst performing an SSL socket operation ". I would like to know why is it happening intermittently and how to find root cause of this issue. While we invoking services in OnPrem instead of AWS all good , when we swith to AWS he are facing the following issue
HTTP Request Node Settings: Protocol - TLSv1.2 ,HTTP Version 1.1
IBM Integration Bus v10.0.0.8 and IBM ACE 12.01
POST //url**** HTTP/1.1 ;A Web Service request has detected a SOCKET error whilst invoking a web service located at host ****t;A timeout error occurred whilst performing an SSL socket operation
BIPmsgs Number :3166
I have application stack consisting of three services in AWS ECS. I have been planning to implement service mesh using AWS App Mesh. I have followed the following instructions to setup the mTLS for my services.
https://awscloudfeed.com/whats-new/security/how-to-use-acm-private-ca-for-enabling-mtls-in-aws-app-mesh
Using the technique mentioned on the blog I was able to setup the mTLS and communication is working fine from virtual gateway to services.
But when one of the service tries to access another service it fails to make connection. Services are built using NodeJS and one service(let's say A) use request library to call service B. From my understanding of the service mesh, the TLS session initiation should start from the envoy proxy of Service A and terminate in the envoy proxy of Service B. In this case I should have used the service discovery url of the Service B (eg. http://serviceb.example.com) when calling it from the serivce A. While doing so, I get ECONNRESET error with message socket hangup. And while using https protocol (eg https://serviceb.example.com) I get ECONNRESET error with message of TLS error.
But if I disable the client certificate requirement for the service B, I am able to access it from service A with https protocol. Does this mean that if i need to set the mtls in appmesh, i will need to load the client certificate through the application itself? I think the request should have gone through without issue as client certificate is provided through the backed client configuration.
Can you help me understand how app mesh mTLS work and if I am missing something while configuring the app mesh?
Thank You
We've configured WSO2 using the below ISO8583 endpoint to receive messages and communicate with a RESTful API.
https://docs.wso2.com/display/ESBCONNECTORS/Configuring+ISO8583+Inbound+Operations
The provider we're integrating with are expecting that we will initiate the connection with their server on the 5000 port, and only then will they begin sending transactions to us. I'm primarily experienced with RESTful APIs so I'm not familiar with WSO2 and opening and maintaining a socket connection. How do I need to configure WSO2 to create and maintain the connection with the host / port from which we expect all transaction to then originate?
I assume this will be via the ISO8583 connector however need guidance.
https://docs.wso2.com/display/ESBCONNECTORS/Configuring+ISO8583+Connector+Operation
Could you please elaborate more on your requirements. While reading the description, I do not think that you have a requirement to consume ISO8583 standard messages. Please use this connector only if you are consuming ISO8583 standard messages.
You can refer to the documentation on the inbound endpoint in document [1] to further clarification regarding the listening inbound endpoint, in which you can define a host and a port. Please elaborate more on the type of messages that need to be consumed how to interact with the backend to provide with a more infomative answer
[1]-https://docs.wso2.com/display/EI650/WSO2+EI+Inbound+Endpoints
I am trying to integrate the Mule Amazon SNS connector behind the corporate proxy and having much trouble to bypass the proxy. It always give me this error:
[[snstest].HTTP_Listener_Configuration.worker.01]
com.amazonaws.http.AmazonHttpClient: Unable to execute HTTP request:
Connection to https://sns.us-east-1.amazonaws.com refused
Exception stack is:
Unable to execute HTTP request: Connection to https://sns.us-east-1.amazonaws.com refused
Failed to invoke createTopic. Message payload is of type: NullPayload
org.mule.modules.sns.processors.CreateTopicMessageProcessor:129
I believe the issue is the proxy trying to block the connection between the application and the amazon endpoint. When I try it at home with direct internet, it worked. Also, I have also tried http:connector and http:proxy to configure the proxy and it has not worked at all.
Check the secret key and access key. Issue is not with proxy its problem in credentials.
I an building a Java EE application with Netbeans 7.3.2 using Javafx as a client to be served by web services from the EJB. I want to add SSL to secure the web services communication with the client over the network. I tried to add security to the web services but getting the following errors
SEVERE: WSS1601: Security Requirements not met - Transport binding configured in policy but incoming message was not SSL enabled
SEVERE: WSITPVD0035: Error in Verifying Security in Inbound Message.
com.sun.xml.wss.impl.XWSSecurityRuntimeException: WSS1601: Security Requirements not met - Transport binding configured in policy but incoming message was not SSL enabled
I have tried all means to get a tutorials online to help me do this since I am new to web services security and more so to configuring SSL for this.
Please can someone please help me with some tutorials or solution to this. Thanks in advance.
Web services are usually normal web applications in the background. So usually it is enough enabling SSL and assigning an SSL port at server side. For example in WebLogic open WebLogic admin console and set the followings:
Environment/Servers/AdminServer/Configuration/SSL Listen Port Enabled
Environment/Servers/AdminServer/Configuration/SSL Listen Port: 7004
Then at client side just change http to https and the non-SSL port to the SSL port in the URL of the web service.