wso2-am

问题 When restarting APIM Analytics the following error appears in log (the first run is ok). We need to truncate ANX___8GEKYOMM_ table for being able to start it again. TID: [-1234] [] ERROR {org.wso2.carbon.analytics.dataservice.core.AnalyticsDataServiceComponent} - Error in activating analytics data service: null {org.wso2.carbon.analytics.dataservice.core.AnalyticsDataServiceComponent} java.lang.RuntimeException at org.wso2.carbon.analytics.datasource.rdbms.RDBMSAnalyticsRecordStore

问题 I have a Spring Security OAuth2 server that generates JWT tokens for frontend applications. This tokens will be sent in the calls to the backends, passing through an API Gateway (WSO2 API Manager). What I would like is to have the backend APIs registered in WSO2 and be able to validate that externally generated JWT token. Is this possible? Can you provide a sample of the different places of the WSO2 APIM that would need to be configured to include this logic? NOTICE: The WSO2 will never need

问题 I have been trying to configure WSO2 API manager as our API Gateway. I am facing below issues while configuring and testing. Authorization of apis migrated to WSO2 Getting JSONObject["exp"] not found. when trying to access API with Token Not sure about the client ID which has to be given for Authorization URL: https://localhost:8243/authorize Is this URL: https://localhost:8243/authorize is the one we use for authenticate the APIs Have used carbon for creating users, Service and Identity

问题 I am testing out the pre-release version 3.0 of wso2 API-M with the generic admin/admin credentials and want to invoke the various publisher apis at http://wso2.github.io/carbon-apimgt/apis/publisher/v1.0/ - e.g. creating a new api. All of these apis take oauth access tokens, however in their documentation I only see the oauth2 scope for them noted, but I don't see how to generate the access token to pass in the api request. It is clear how to generate oauth tokens for apis and apps already

问题 I have installed the api manager on a windows server 2008. The server has a LAN-IP and a Public-IP over NAT. Example: LAN-IP: 192.168.100.1 Public-IP over NAT: 10.0.0.10 I want to test the API Manager over the Public-IP, but the Server works only local with the LAN-IP. Has someone an idea, how can I get the api manager to work over the Public-IP? The Ports are open on the firewall. THX 回答1: Please try out with the following configurations. Note to restart the server once done. Set the

问题 I'm unable to login to admin dashboard in WSO2 API manager. I got an error "Unable to log you in! Login Failed " API Manager is configured with LDAP read only primary user store. Our LDAP do not have groups and roles are not red from LDAP. Additionally API Manager is configured to work with MySQL DB and WSO2 IS as key manager. But I think this is not a reason of such behavior. If I configure API Manager with a standard user store (without any changes to user-mgt.xml) login to admin-dashboard

问题 Closed. This question is off-topic. It is not currently accepting answers. Want to improve this question? Update the question so it's on-topic for Stack Overflow. Closed 5 years ago . I have configured API Manager 1.6.0 with MySQL. I have tried to run the version 1.7.0 with same conections and I have several errors like this Caused by: com.mysql.jdbc.exceptions.jdbc4.MySQLSyntaxErrorException: Table 'wso2_apiManagerdb.IDN_OAUTH2_SCOPE' doesn't exist Exists any documentation for migrate?

问题 I have the WSO2 API Manager running on a Windows 2012 R2 server and all dashboard URL's like https://localhost:9443/store , https://localhost:9443/carbon , https://localhost:9443/publisher work fine. But when I configure and deploy (in the carbon.super tenant) the example WeatherAPI web service and try to reach it via the /services/... URL i.e.: https://localhost:9443/services/weather/1.0.0/*?q=Amsterdam I get the following error page returned: > HTTP Status 500 - > > > type Exception report

问题 I've been using WSO2 API Manager 1.9.1 for the past month on a static IP and we liked it enough to put it on Azure behind a full qualified domain name. As we are still only using for internal purposes, we shut the VM down during off hours to save money. Our Azure setup does not guarantee the same IP address each time the VM restarts. The FQDN allows us to always reach https://api.mydomain.com regardless of what happens with the VM IP. I updated the appropriate config files to the FQDN and

问题 I'm using WSO2-APIM-2.1.0 . Which internally uses solr 5.2.1 . Inside WSO2-APIM-2.1.0 , I've added around 2087 applications. Wso2 internally generating the solr OR query which has around 2087 OR clauses of 121825 characters. When I tried to get application list though the API call: curl -k -H "Authorization: Bearer access_token" "https://localhost:9443/api/am/publisher/v0.11/subscriptions?apiId=apiId&limit=2200" (It took around 6 minutes, which is too long.) Using the link https://localhost