wso2

问题 In a connection to a server we get errors such as: <errorCode>101500</errorCode><errorMessage>Error in Sender</errorMessage> Is there a way to get more information on the cause, except from "Error in Sender"? Note: In the SSL transport sender I have set AllowAll for the HostnameVerifier <transportSender name="https" class="org.apache.synapse.transport.passthru.PassThroughHttpSSLSender"> <parameter name="non-blocking" locked="false">true</parameter> <parameter name="http.proxyHost" locked=

问题 I have created custom mediator with Factory and Serializer classes. Created jar with \META-INF\services\ files and put it to dropins folder. But after restart when I deployed test proxy with my mediator, I always get error like this: org.apache.synapse.SynapseException: Unknown mediator referenced by configuration element : at org.apache.synapse.config.xml.MediatorFactoryFinder.getMediator(MediatorFactoryFinder.java:218) It looks like ESB isn't able to find the Factory class. Where is my

问题 After add configuration for enable WSO2 Is-Analytics v5.8.0 in deployment.toml file in the IS_HOME/repository/conf/ directory https://is.docs.wso2.com/en/5.10.0/learn/configuring-identity-analytics/ And than running wso2server.bat IS_HOME/bin directory. When trying to access the application in service provider, an error was found any advice how to fix an error? thank you 回答1: First step Configure according to the following link for analytics https://is.docs.wso2.com/en/5.10.0/learn

问题 After add configuration for enable WSO2 Is-Analytics v5.8.0 in deployment.toml file in the IS_HOME/repository/conf/ directory https://is.docs.wso2.com/en/5.10.0/learn/configuring-identity-analytics/ And than running wso2server.bat IS_HOME/bin directory. When trying to access the application in service provider, an error was found any advice how to fix an error? thank you 回答1: First step Configure according to the following link for analytics https://is.docs.wso2.com/en/5.10.0/learn

问题 I am having a requirement to publish all APIs developed to run on ports 80 and 443 instead of 8280 and 8243. I changed the axis2.xml as below and restarted the API Manager server. <parameter name="port" locked="false">80</parameter> <parameter name="port" locked="false">443</parameter> I can see published APIs in API store showing 80 and 443 ports respectively. But when I am trying to test it using Postman like below URL, it throws the below error. URL: http://localhost:80/pizza & https:/

问题 I'm using APIM-3.1.0 and I need to Redirect APIs’ based upon header or request parameter. I have tried for request parameter but unable to call different API's. I have used below custom mediation policy and added it to a test API, but unable to call the different URLs. Every time I was calling API, I was getting output for the else part (URL mention in the else part) in below code even if I am passing the value of operation as menu. <sequence xmlns="http://ws.apache.org/ns/synapse" name=

问题 I'm using APIM-3.1.0 and I need to Redirect APIs’ based upon header or request parameter. I have tried for request parameter but unable to call different API's. I have used below custom mediation policy and added it to a test API, but unable to call the different URLs. Every time I was calling API, I was getting output for the else part (URL mention in the else part) in below code even if I am passing the value of operation as menu. <sequence xmlns="http://ws.apache.org/ns/synapse" name=

问题 Is it possible to remove security for some specific requests in my api list using WSO2 API manager version 3. For example, I have following requests /customer - post /products - get /customer/address - get In my case I don't need security for /products - get . Update I tried the suggestion @Pubci getting request response Invalid Credentials. Make sure your API invocation call has a header: 'Authorization : Bearer ACCESS_TOKEN' or 'Authorization : Basic ACCESS_TOKEN' or 'apikey: API_KEY 回答1:

问题 I am using WSO2 IS 5.10.0 running in the official Docker image and followed the guide here to setup session limiting for users with defined roles. I have attempted to use the main way described in the article (using the active-session-limit-handler), as well as the alternative method described in section 2 (using adaptive authentication Javascript functions). Neither method has worked for me. Through error logs I was able to trace the issue back to the following query: SELECT USER_ID FROM IDN

问题 We are using WSO2 SCIM apis to define roles to user and update it. For role update operation , we are currently adding the new user role(add user to new role group using SCIM api) , and then delete the existing user role (call users SCIM GET request under a GROUP, delete the existing user from the list and use the newly created list as body arguments to call SCIM PATCH request for the GROUP). With this approach , we were able to update roles. But as the user base increased , the above