wso2-am

WSO2 API Manager compatibility with Python

橙三吉。 提交于 2019-12-25 15:41:30
问题 I want to know if WSO2 API Manager is compatible with Python and PHP based restful services or not? I have several webservices which are developed on JavaEE, Python and PHP. Except JavaEE, no other platform is communicating with WSO2. On Python, I don't receive any RAW payload in my POST requests from WSO2. These services are working fine and can communicate with them via REST Console. Please see my other STACKOVERFLOW POST for details. I need to know how I can consume Python services just

SAML2BearerGrantHandler unable to verify signature

前提是你 提交于 2019-12-25 08:21:33
问题 I'm trying to get the SAML2BearerGrantHandler in APIM 2.0.0 up and running. I'm using Auth0 as the IdP with their SAML2 add on. I've created the IdP in carbon console, uploaded the signing cert etc. I sort of followed this document to test the grant: https://docs.wso2.com/display/AM200/SAML+Extension+Grant I get back an assertion, but when I try to get a token, I get this error: [2016-12-22 14:14:07,493] DEBUG - Starting to unmarshall Apache XML-Security-based SignatureImpl element {org

UserRegistry Attempted to authenticate invalid user

浪子不回头ぞ 提交于 2019-12-25 08:20:06
问题 I followed https://docs.wso2.com/display/CLUSTER44x/Clustering+API+Manager+2.0.0 and http://wso2.com/library/articles/2016/10/article-scalable-traffic-manager-deployment-patterns-for-wso2-api-manager-part-1/ referenced in the above document. I am using Postgress and not MySQL, but I know the JDBC connector works, both in this config and running the wso2am server in a single instance mode. I get the error mentioned in the subject. I start the keymanager, then traffic manager with ./wso2server

WSO2 API Manager 1.10 issue

。_饼干妹妹 提交于 2019-12-25 07:58:34
问题 We are running into an issue where a call to a WSO2 API REST endpoint fails with a "412 Precondition Failed" when the Content-Length exceeds 1068. Just adding a space to the request (increasing size to 1069) causes this failure. This issue can also happen when content length is less than 1069, if the API is called fast enough (using SOAPUI for testing). We have a theory that the header and body are split between packets and confuses the request. We tried turning off chunking and that didn't

WSO2 API Manager v1.8.0

喜你入骨 提交于 2019-12-25 04:47:14
问题 I have a simple use case of mapping path param from the API consumer to the backend API endpoint. I have done a lot of research but have not found out the specific answer on how to do that. As per my understanding, thr mapping of the path parameter can't be done without the use of uri-template. Now the problem is that the API Manager does not support uri-template from the API Publisher user interface and you have to use url-mapping instead. One blog from WSO2 developer says that you can then

Authorization Bearer in URL Request using WSO2 API Manager

半世苍凉 提交于 2019-12-25 04:26:28
问题 Is there a way to put the authorization bearer in the URL request? The curl command to access my API is this: curl -X GET --header 'Accept: application/xml' --header 'Authorization: Bearer ebcd41ac-3466-3262-8c8e-3c73c987dbde' 'https://gateway.api.cloud.wso2.com:443/t/jab7180/prod/1.0.0/inquire/promos/IBM' But if I use the request URL in my browser using https://gateway.api.cloud.wso2.com:443/t/jab7180/prod/1.0.0/inquire/promos/IBM, I am getting this error message: Code = 900902 Message:

Getting Response code 0 in API manager wso2 while Trying to connect Through enterprise Proxy

半城伤御伤魂 提交于 2019-12-25 03:38:23
问题 Well , i m hitting a simple PhoneVerify Request from my localhost which have enterprise proxy . i have configured my Proxy setting using below link. Can't access to production endpoint with WSO2 API Manager - entreprise proxy But I m Getting The Same Response code 0 and Blank Response Body. Here Is a the curl and Request URL : Curl curl -X GET --header "Accept: application/json" --header "Authorization: Bearer b9d93ac569bec1721716e1422b852b" "https://192.168.78.153:8244/phone/1.0.0

What's the recommended way to define URL patterns and versioning for backend services and API definitions in WSO2 API Manager

折月煮酒 提交于 2019-12-25 03:35:24
问题 We are facing a problem when including our Java application services in WSO2 API Manager. Our typical backend applications runs on Tomcat and has a context path, e.g. (/customer-manager). Its Spring controllers define endpoints with this format: /api/VERSION/resource , e.g: /api/v1/customers , /api/v2/customers , etc. Thus, our calls to the backend look like this: http://localhost:8080/customer-manager/api/v1/customer . Our autogenerated swagger documentation publishes the REST path

Can't login WSO2 API manager via wso2 identity server and Facebook credential

ぐ巨炮叔叔 提交于 2019-12-25 01:15:38
问题 What I wanna do is : 1.SSO with wso2 Identity server 5.1.0 and wso2 API manager 1.10.0 (done) reference : https://docs.wso2.com/display/AM1100/Configuring+Single+Sign-on+with+SAML2 2.Login wso2 API manager 1.10.0 via Facebook credential (fail) reference : https://docs.wso2.com/display/IS510/How+To%3A+Login+to+the+Identity+Server+using+Facebook+Credentials The situation is : 1.When I go to the login page of APIM , it will redirect to Facebook login page via Identity server. 2.I login to

WSO2 APIM Custom sequences for non published APIs / Setting variable

旧时模样 提交于 2019-12-24 23:26:49
问题 We have defined a default custom sequence for managing different gateways, as described here We have installed the sequence as explained in the doc Creating Global Conection The sequence only read 2 variables from environment, and uses to build the endpoint URL. This is the code: <sequence xmlns="http://ws.apache.org/ns/synapse" name="WSO2AM--Ext--In"> <property name="uri.var.host" expression="get-property('system','host')" /> <property name="uri.var.port" expression="get-property('system',