when I ran the gateway server it shows this error "This data graph is missing a valid configuration. unreachable"
I solved this by upgrading apollo gateway to the latest version
Thanks, I solved it by trying different versions of Apollo federation & gateway ( the latest version didn't work for me )
Related
I'm trying to use the REST API for BPMN following the documentation, but even the most basic requests such as
https://localhost:9443/bpmn/repository/deployments
or
https://localhost:9443/bpmn/repository/process-definitions
return the following error
{"statusCode":400,"errorMessage":"javax.ws.rs.InternalServerErrorException.validate(Ljavax/ws/rs/core/Response;Ljavax/ws/rs/core/Response$Status;)Ljavax/ws/rs/core/Response;"}
I'm using BPS server 3.5.1 with Oracle JDK 1.8.0_77, as it was downloaded, with the only addition of a BPMN process to test its dashboard. The service is run as root (via sudo)
What can be done to fix this?
Thanks
I tried it on postman and it works perfectly. Please choose the correct request type (GET, POST, PUT or DELETE), if not the following error will be thrown on the server side:
javax.ws.rs.ClientErrorException.validate(Ljavax/ws/rs/core/Response;Ljavax/ws/rs/core/Response$Status$Family;)Ljavax/ws/rs/core/Response;
I am using amazon web apis to generate federated user credentials e.g. GetSessionToken. It's working fine on my localhost machine but throw error on live server . Any guesses?
Error throws:
A WebException with status TrustFailure was thrown.
That does not sound like an AWS exception. It sounds like an SSL/TLS issue related to certificates.
I had a similar issue - is your date correct on your machine?
The AWS connection process will throw out the request if the date is wrong.
I answered a very similar issue here . In my case, the server I was receiving the error on did not have the correct cert in its trusted root certificate authorities. Adding the correct cert resolved the issue.
check certificate settings installed on Production machine
I am using WSO2 API Manager (1.8) and WSO2 BAM server(2.5.0) . I have done the
following configurations for getting statistics.
Configurations in :
https://github.com/Prasanthmv/Wso2/blob/master/configurations/all.doc
After that I started BAM and AM, but the following error appears :(I have
pushed the error in github):
AM error
BAM error
Why this error is showing, is my configuration
correct?
Here's documentation on how to set up API Manager / BAM integration: https://docs.wso2.com/display/AM180/Publishing+API+Runtime+Statistics
Alternatively, you can use WSO2 API Cloud (SaaS version of API Manager) in which everything is preconfigured and works out of the box.
According to the carbon logs, You must be using windows 7.
Therefore,
This could be due the BAM cannot execute cygwin commands. Please try to install Cywin into C drive and make sure no space in file path and append "C:\cygwin64\bin" to the windows PATH (using "Edit the system environment variables").
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....
When I try to config throttling with domain type in WSO2 ESB 4.0.3 for services ECHO.
I tried to send the soap message from client to server via command line:
curl --data-binary #soaptest.xml -H 'Content-Type: text/xml;charset=UTF-8' "http://dc2nix2d11:8282/services/echo"
But I still get the result although I set access deny for the domain of client machine.
I try to do the same config throttling with IP type and it's work.
Maybe Throttling does not work with domain type in WSO2 ESB 4.0.3 ?
Please help me to fix this issue.
This is an known issue. It's already fixed in next ESB release
If you are using service hosting feature on WSO2 ESB you could alternatively use recently released WSO2 AS 5.1.0 which support for domain based throttling to host your services till the next ESB version get released.