wso2-am

问题 Using WSO2AM-2.6.0, we are trying to encrypt userstore credentials for a primary LDAP userstore manager. Encrypting credentials well works for the realm config credentials (admin password), jndi properties, api-manager.xml, datasource credentials. What we have issue with is the primary userstore LDAP connection credentials (as the user is as well an admin user) In theory there are comprehensive guides as well some older questions such as here How to encrypt LDAP UserStore password in usr-mgt

问题 can I create scopes programmatically in WSO2 APIM? I have a requirement where user can create new roles via UI and associate some permissions with the new role..User will not use WSO2 web interface ; rather he will use the inhouse web application For this, I have to programmatically create Scopes and associate API's with it. Also manually map scopes to roles. How can I create scopes via WSO2 APIM Programmatically? What all the operations possible with scopes programmatically? If it's not

问题 I have an answer which can disable unwanted protocols/ciphers (TLSv1.0 and 3DES based ciphers) for management console in Tomcat(port: 9443), Disable weakened protocols/ciphers in WSO2AM-1.10.0. however, I have no idea how can I apply the same settings to API connection in Axis server (Port 443) like below, The API connection using 443 port seems still support TLSv1 as tested by sslsscan, Thanks,Sean 回答1: You need to change the following pass-through settings in repository/conf/axis2/axis2.xml

问题 When setting up an application from the API Manager store how can I make the OAuth2 grant types authorization code and implicit the defaults for the app? I know how to do this manually using the carbon interface but I would like to make the two grant types the default. 回答1: For authorization code and implicit grant types to be enabled by default, you need to specify a callback URL when creating the App on store. When the callback URL is available these 2 grant types will be shown as enabled

问题 I'm having another problem using WSO2 API Manager 2.0.0: I have installed it in docker using three containers (one for APIM, one for Analytics and one for MySQL) and I replace some configuration files with my custom version (e.g. DB, server name, gateway setup...). Both APIM and Analytics are configured to save data in the MySQL container and I am able to see changes in the DB. The issue is that I cannot find my APIs neither in the publisher nor in the store after the container has been

问题 I am trying to do something that seems straightforward but can't get it to work. Basically I want the WSO2 API manager to add a URL parameter to a REST call. Setup and Problem I have a WSO2 API manager installed. I also have a Tomcat running with a bogus servlet called someservlet that simply logs anything it receives and returns ok. I have added the servlet as an API in the manager, so I can either call the servlet directly or via WSO2 API mgr. I can run curl http://localhost:8080

问题 What is the recommended way for validating that a JWT was issued by a specific API Manager instance in a case where the backend web service lives on a separate server and needs to be certain that a given request passed through the APIM Gateway authentication and authorization mechanisms? I know that the header fields in the JWT include an 'x5t' field which is an encoded reference to a certificate in the tenant key store, as detailed here: https://asankastechtalks.wordpress.com/2013/12/05

问题 We are evaluating the WSO2 API Manager 1.8.0 (WSO2 AM) together with the WSO2 Business Activity Monitor 2.5.0 (WSO2 BAM). From our support partner Yenlo we got the WSO2 recommendation to use WSO2 BAM 3.0 for new installation, because the changes from BAM 2.5.0 to BAM 3.0.0 are massive. BAM 3.0 is not released yet (see the release plan in JIRA). But milestone 4 should be available. But the only thing I can find is milestone 3 of BAM and milestone 4 of DAS (Data Analytics Server) as announced

问题 We are using WSO2 ESB 4.7.0 and WSO2 API Manager 1.6.0 I have an API defined the ESB which takes a PUT request and processes it to a back end system and sends back the response as success. The API works fine if I use the soap client or Advanced Rest Client. Request URL: http://:/CurriculumAdmin/Terms/2010/Classes/11513/LMSURL?LMSURL=KRanthiPUTARCAPI Response: Status 200 OK But if I create a API using the WSO2 API manager and use the try it option from there, I get a 202 response Request URL:

问题 How to access response payload content from custom handler in WSO2 APIM? I tried get this from org.apache.synapse.MessageContext or from org.apache.synapse.core.axis2.Axis2MessageContext; but I am not able get the response payload. Can anyone please help? 回答1: You need to build the message inside you handler before reading the payload, as shown below. public boolean handleResponse(MessageContext messageContext) { try { RelayUtils.buildMessage(((Axis2MessageContext) messageContext)