I have a web service installed on Tomcat. I am using HTTPs to call the web service using a self-signed certificate. Calling this web service through HTTPs from PHP (curl) works fine and I get a normal response.
However, when the same HTTPs is sent to a USSD gateway, it does not return any response. It does with the normal HTTP requests.
I am not familiar with the gateway or its implementation. I only wrote the web service to be called but is there a way that the gateway can ignore the "untrusted certificate error" and proceed to send the HTTPs request to the Tomcat server?
Thanks.
Related
Currently I am using the API Gateway as a kind of proxy to provide https simply
https://random-aws-name.com => http://my-domain.com
The route was $default
The integration setup is HTTP ANY -> http://my-domain.com
I am now having to setup an Websocket server on my domain that is already listening at ws://my-domain.com. I can connect directly to this socket but not using the AWS API Gateway
wss://random-aws-name.com => ws://my-domain.com
Currently I an getting unexpected error 400, using wscat
I tried to enable API gateway logging and do not see any log arrive
IMHO, AWS API Gateway is only able to provide a wss end point and route requests to HTTP backends only. If we already have a backend websocket server, I don't see an option in AWS API Gateway to perform such routing (Although I would be glad to be proven wrong as I have such a requirement myself.).
I actually tried giving wss:// url as the Endpoint URL but I got an error while deploying the API saying Invalid HTTP endpoint specified for URI
Most likely, the API Gateway you are currently using is not a WebSocket API, but rather an HTTP API or REST API. API Gateway has different flavors. You pick a flavor when you deploy. The flavor that you deployed is most likely not the flavor that supports WebSocket connections.
According to this documentation page, proxied WebSocket connections may only be one-way (note in blue box at bottom of page): https://docs.aws.amazon.com/apigateway/latest/developerguide/apigateway-websocket-api-routes-integrations.html
I have a web app which consists of 2 parts, front-end(hosted on host gator via https) and a back-end on AWS.
At first I got 'Mixed Content' error when I tried to connect my https front-end to my http back-end on elastic beanstalk, so I got myself an ssl certificate from ACM and applied it to my http back-end using load balancer, so now I can access back-end via the same link but with 'https' instead of 'http', but I get this error in the browser 'Your connection isn't private, NET::ERR_CERT_COMMON_NAME_INVALID', and I have to proceed manually, same happens with my front-end when I connect it to the new https link, as I get this error in the console.
what should I do?
I can make HTTP REST call inside a BPM Process. How do I do a secure HTTPS call. In Oracle I have to add the certificate to a wallet and then make the call. So how do you do that in WSO2 as it fails if I change the URL from HTTP to HTTPS ?
You have to import the certificates to client-truststore as in this documentation.
How to publish only Http service from WSO2AM?
I am receiving an empty response from the server when I access WSO2AM service from my client.
This is what I am setting for HTTP. Service is working using HTTPS but that is not desired.
I have generated a JAX-WS web service with RAD 8.5 which automatically generated an endpoint for the service at "http:endpoint". I generated a client for the web service from the WSDL and added transport security (SSL) to the web service and added a secure endpoint using the following line of code in my client:
proxy._getDescriptor().setEndpoint("https:endpoint");
Everything seems to work fine. My question is do I need to do anything about the existence of the original endpoint ant "http:endpoint". This is an in-house web service so all of the apps which use it in house will use the secure endpoint, but is the availability of the unsecure endpoint a security risk for the web service? If so, what do I need to do to fix it? Any help would be appreciated.
I am not familiar with the Framework you are using, but there should be a configuration in your proxy to not allow http calls at all. If you have that option, turn it on so that your service only listens on port 443 (secure port).
An alternative would be to rewrite all http requests with https.