I am trying to use Google Cloud Endpoints as a API Gateway. For the same I created the endpoint and deployed it in a Google Run Container. When I call the url on the browser: https://... it works. However, when I try to call the same from Postman I get a 400 Bad Request error. I notice that from Postman when I try using http://... instead of https it works.
From this I concluded that perhaps this has something got to do with the SSL certificate. When I checked the certificate on the browser (by clicking on the lock icon), it shows *.a.run.app issued by GTS CA 1O1.
Then, I tried to add a Certificate in Postman (I am not sure about this). I opened Settings and tried to add a certificate by adding: *.a.run.app under host, but it did not work. I am not sure if that is the correct way to add a certificate.
Anyone can suggest what is the way to get the endpoint tested in Postman? Thanks
Related
I have a Flutter Web application that I have deployed on Firebase Hosting.
I have a Django backend that I have deployed on an EC2 instance and is running on http.
I have CORS enabled in the backend, tried accessing endpoints via browsers and it works just fine.
But, when I try to make the same call using FlutterWeb, it fails.
And error type of blocked:mixed content appears. (See image below)
I want to call those HTTP endpoints and I don't want an SSL certificate mess because this is just a college project. How do I fix this?
I am using Dio on Flutter Web to make requests. What would be causing this problem?
EDIT:
I am using Firebase's spark plan, obviously since it's a college project. Do I need to upgrade to the blaze plan to enable Egress traffic? If so, how do I make sure that I won't be heavily charged? Any suggestions? UPDATE: I tried the blaze plan and got the same issue.
The console says
Mixed Content: The page at
'https://xxx.web.app/' was loaded over HTTPS, but
requested an insecure XMLHttpRequest endpoint
'http://xxxx.compute-1.amazonaws.com:8000/menu'. This
request has been blocked; the content must be served over HTTPS.
Any way to bypass this?
I am on Postman 7.5.0.
I am calling one api from the postman, and get an error as "There was an error connecting to ."
But when I executed the curl code generated from the postman, it worked just fine(they were also calling the app running on my pc).
I also tried to copy the link and sent to my coworker and they were getting correct responses too.
I referred to other questions related to this topic and turn off all proxy stuff, they didn't help.
My app has lots of apis and this is the only one that I could not get any response via postman call.
Any thoughts?
In my case I had to go to Settings -> "SSL Certificate Verification" and turn this off, and everything worked great.
Have you used chrome extension Postman Interceptor?
I think Postman is not able to intercept https or http request.
Follow the steps:
To use Interceptor with Postman Chrome, you can take the following steps:
Install Postman from the Chrome Web Store.
Install Interceptor from the Chrome Web Store.
Open Postman, click on the Interceptor icon(near the sync icon) in the toolbar, and toggle to On.
The Postman Chrome app's Interceptor functions as a proxy to capture HTTP and HTTPS requests.
More Information is available at https://learning.postman.com/docs/sending-requests/capturing-request-data/interceptor/#using-the-interceptor-with-postmans-chrome-app
For my case, it was me mistakenly unchecked one of the postman default headers.
I have deployed the a rest webservice over https using self signed certificate. Now i am facing the issue in postman while trying to test it. Error is same as follows:-
I also follow the post from this link using-self-signed-certificates-with-postman but i am not able to find the connection tab as mentioned in the step 3.
Can anybody please help me how can i resolve that certificate issue.
Thanks
Try open the same URL in your chrome browser. You may get privacy
error. Click advanced link and proceed. Come back to postman and
send your request.
In Postman go menu File/Settings in General tab disable "SSL certificate verification".
I am configuring our API Manager, but running into troubles authenticating via OAuth, seems to be an issue with the API Key Manager. I haven't dug into it yet, but does this come with the API Manager (as I have assumed) or is this a separate installation?
I had the same issue when using the wso2 api manager on a Amazon hosted machine, turn out that Thrift was not working correctly because some problem with multicasting and broadcasting.
What I did to get it working was to switch from ThriftClient to WSClient. If you have a huge amount of requests coming in then Thrift is the recommended solution from wso2 but in any "normal" case you will not have any differences between thrift and WS.
Here is how you switch:
Shut down the API Manager
Open up <api manager install dir>\repository\conf\api-manager.xml
Find ThriftClient
Change this to
<KeyValidatorClientType>WSClient</KeyValidatorClientType>
Start the API Manager
You may get some Warnings while starting up but, try it before you jump to the conclusion that it doesn't work.
Hope it helps!
you can use APIM manager product in a distributed setup as keymanger,gateway,store,publisher..but all functionality come in a single distribution.. ..
Go through the documentation for further guides
I was facing the same issue. Everything started when I created my own jks in order to use SSL without a self-signed certificate. I successfully created the jks and changed it in the carbon file. When I started the server, everything seemed ok; but when I used SOAPUI to test an API call, I got this (in the logs of the api manager):
APIAuthenticationHandler API authentication failure due to Unclassified Authentication Failure
I started digging what was the problem by enabling Debug level in the log4j.properties file, and then tried again a tested with SOAPUI and I got:
APISecurityException: Could not connect to <my api ip address> on port 10397
Then, I read the comment of OneMuppet and I checked that file and I found that the Thrift config has a host option, so I uncommented it:
<KeyValidatorClientType>ThriftClient</KeyValidatorClientType>
<ThriftClientPort>10397</ThriftClientPort>
<ThriftClientConnectionTimeOut>10000</ThriftClientConnectionTimeOut>
<ThriftServerPort>10397</ThriftServerPort>
This Line --> <ThriftServerHost>localhost</ThriftServerHost>
<EnableThriftServer>true</EnableThriftServer>
Save, restarted the server and everything start working correctly.
I got the same below issue after my installation, when i try to invoke the api service it is throwing below error:
900900 Unclassified Authentication Failure Error while accessing backend services for API key validation
After some random checks i have seen the axis2.xml file in /repository/conf/axis2 there it is refering a differnt ip's instead. I change these ip's to my local ip and restarted. The issue is resolved now.
I was facing the same issue. when I was trying to setup API Manager as an API Gateway in a different machine as per the steps given here,
https://docs.wso2.com/display/AM250/Publish+through+Multiple+API+Gateways
Once the setup is done and when I am trying to use this gateway URL, I was getting the below response,
{"fault":{"code":900900,"message":"Unclassified Authentication Failure","description":"Error while accessing backend services for API key validation"}}
After changing the KeyValidatorClientType value to WSClient from ThriftClient on the <api manager install dir>\repository\conf\api-manager.xml
It started working fine. And I was able to get the expected response.
If you changed the admin password, then you also have to update the repository/conf/api-manager.xml file with the new password. The 2 places I have changed (so far) are:
<AuthManager>
and
<APIKeyManager>
but there are other admin usernames in that file. No doubt, I'll get to them....
I keep getting Connection Failed when trying to request data from a page that is on an https:// domain. I did install the ssl cert using the built-in section of the railo admin at https://[mydomain]/railo-context/admin/server.cfm?action=services.certificates however I still get Connection Failed. How should I go forward with debugging this? I have confirmed that this server in particular does have access to the domain I am trying to request from.
You probably need some additional certs installed as Jason has said. Take a close look at the cert and it's chain. Go to the cert issuers site and look for some documentation.
To troubleshoot you can add some logging to your jvm args. I think it's something like:
-Djavax.net.debug=all
The results are either in the OUT log or the server.log. This post on SSL 3.0 has some debugging tips. It's possible that your cert needs to handshake at a lower security level than CF allows (SSL 2.0 instead of 3.0/TLS for instance) and that could cause this behavior - but it's more likely that you simply need an intermediate cert installed.
The problem ended up being the permissions weren't setup properly on the machine. After we had the server administrator fix our permissions to access the Railo-Tomcat Service Control, the requests started working. I'm assuming he fixed some other permissions while he was in there.