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 writing a 'Content Script' based extension for Chrome that works on GMail (HTTPS). It needs to access a web service on our website, which is currently on HTTP only. Other than getting an SSL, is there any alternative to get an AJAX GET/POST call working between these two?
I think you can : https://developer.chrome.com/extensions/xhr
But be aware that without https someone can see and change everything your extension send or receive with your website.
You should implement https as soon as possible to avoid any security issue.
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 am looking at http://wso2.org/forum/thread/10508 which explains how to get the HTTPServletRequest. It explains that if you have "org.wso2.carbon.core.transports.http.*" request then only you can get the HTTPServletRequest object. As described I did change the axis2.xml to change the transports and it worked. But then since "org.apache.synapse.transport.nhttp." (NIO) trnasport are very fast I will be loosing the performance if I do that.
Is there any way of keeping the NIO transport handlers ("org.apache.synapse.transport.nhttp.") and get the HTTPServletRequest object?
I would be thankful if I can get the answer. All the authentication is done through cookies in the existing Data Services and company does not want to change that.
thanks
Abhijit
This is not possible. NIO transport is not a servlet and it does not support http sessions and all. But with the new wso2 server version we have upgraded the tomcat version so that even the normal http transport uses NIO underline.
I think you need to do a performance comparison and see with the latest release.