wso2-am

问题 I'm performing WSO2 API manager + Analytics 2.0 POC now. When i change datasource from H2 to Oracle, in wso2am-2.0.1-SNAPSHOT, there are 2 data source config files: master-datasources.xml & metrics-datasources.xml, according Installing and configuring the databases, there should be WSO2AM_DB, WSO2UM_DB and the WSO2REG_DB datasource configurations, but i just find WSO2_CARBON_DB & WSO2AM_DB, so my questions are Is WSO2_CARBON_DB = WSO2UM_DB + WSO2REG_DB ? for WSO2_METRICS_DB , according

问题 I am trying to see how XACML can be used with the API Manager for controlling access to some of the resources. I have followed the blog post here, http://wso2.com/library/articles/2014/02/use-of-wso2-api-manager-to-validate-fine-grained-policy-decisions-using-xacml/ I have also tried following one more post from the following link, http://niranjankaru.blogspot.fr/2014/11/user-role-based-access-to-api-using.html Also, I have gone through most of the Stackoverflow question regarding this topic.

问题 I need to add a custom handler and APIAuthenticationHandler to a specific API and it needs to be added below the handler class="org.wso2.carbon.apimgt.gateway.handlers.security.APIAuthenticationHandler"/> (Note that APIAuthenticationHandler is called twice here, it's a custom requirement) How can I do this programmatically by editing the velocity_template.xml I'm using API-Manager 2.00 Thank you 回答1: You can use API custom properties for this. Add a custom property (e.g. auth_mode=Inhouse )

问题 How can I disable HTTPS for WSO2 Api Manager (admin/gw/other components)? We want to SSL-terminate on our front load-balancers - and not on the end WSO2-products. If I visit port 9763 I'll get redirected to 9443. We're running 2.1.0 deployed with the docker-images. 回答1: You have to do the following, Go to the $WSO2_HOME/repository/conf and open carbon.xml, and uncomment <EnableHTTPAdminConsole>true</EnableHTTPAdminConsole> Disable secure cookie parameter in $WSO2_HOME/repository/conf/tomcat

问题 I am doing some very simple script mediation as a test to see if I can change the payload being returned by my server. My unmediated payload comes out as: {"origin":"202.37.75.130"} Then I try doing a very simple check to see whether get and set work for payloads: <script language="js"> var older = mc.getPayloadJSON(); var newer=older; mc.setPayloadJSON(newer); </script> My result from this is: {"jsonObject":""} I have done testing that shows that setPayloadJSON() works, which means that my

问题 I now have a NodeJS REST API. It is CRUD service. Does anyone know how to secure/protect my APIs step by step with wso2 OAuth2? 回答1: If you simply want to protect your REST API with OAuth2 use the WSO2 API Manager. You can follow the quick start guide to get started. Details related to adding your API and enabling OAuth2 protection is mentioned here in the quick start guide. 来源： https://stackoverflow.com/questions/42569535/how-to-protect-rest-api-with-wso2-is

问题 UPDATE: We have reproduced the same problem connecting to EI 6.1.1 business process module We are trying to implement a application registration (generation of key) for API manager (version 2.1.0), using BPS (version 3.6.0). For this, we are following the instructions in https://docs.wso2.com/display/AM210/Adding+an+Application+Registration+Workflow We have also corrected a typo in the content of the package, as provide by the https://github.com/wso2/product-apim/pull/2730/files#diff

问题 I am using WSO2 APIM (2.5.0) and IS (5.6.0). They both are integrated and working well. Now, if I onboard an third party API in API Management and using oauth token I can be able to access it. But question is how to handle any external or third party APIs which has its own authentication. SO basically, using WSO2 APIM token I can be able to access the onboarded API to use but we will not be able to get any response as the onboarded API has its own authentication (basic or oauth). How to

问题 I created API with WSO2 APi Manager Publisher. Then I subscribed and invoked this API with Integrated API console. All worked OK. Request URL was like: https://host,-name:8243/..... Later I unsubscribed, edited this API a little, published and subscribed. Now, when I invoke API with API console port number in URL is changed from 8280 to 9443 and, of course, API doesn't work. When I invoke API in (for instance) Postman with right port number, API works properly. When I delete API and create

问题 I'm trying to setup a proxy for my RESTful API using WSO2 API Manager. My problem is that the responses from the backend API are left untouched so all the urls that connect to other endpoints still reference the backend server rather than the proxy. I need a way to replace those url values in the response body to point to the proxied api. I understand this can be accomplished via Mediation Extensions, using ESB Mediators. I'm not familiar enough with them to pick the one better suited for the