wso2

问题 We are using WSO2 ESB and as transport we have WebSphere MQ which is accessed using JMS. Problem is that each proxy service works in one thread with WebSphere MQ and because of that we have performance issues. How can we start multiple instances of proxy service without deploying multiple copies of it? Maybe there are some hidden configuration parameters? 回答1: In addition to already mentioned parameter <parameter name="transport.jms.ConcurrentConsumers">2</parameter> you might need to add

问题 I have a simple Proxy Service deployed on WSO2 ESB. The service is defined as follow: <?xml version="1.0" encoding="UTF-8"?> <proxy xmlns="http://ws.apache.org/ns/synapse" name="HelloWorld" transports="https http" startOnLoad="false" trace="enable" statistics="enable"> <description/> <target> <endpoint> <wsdl service="HelloWorld" port="HelloWorldImplPort" uri="http://myhostname:9001/HelloWorldInternal?wsdl"> <suspendOnFailure> <errorCodes>101508,101505,101503,101504</errorCodes>

问题 We are using WSO2 for authentication (SAML/SSO). I don't know how to tell if a user is already logged in (in order to prevent concurrent logins). Other SO questions have indicated this is possible to know both with WSO2 IS Analytics and without. I would prefer to not have to run WSO2 IS Analytics as well (this is alluded to here, but never clarified. Further, I can see the IDN_AUTH_SESSION_STORE table being populated and referred to during login, but that is using SESSION_ID (which is passed

问题 We are using an automation process currently in our environment. We have WSO2 5.3.0. I need to configure Oauth2/Openid Service Provider using XML configuration files. All the documentation, examples, etc, is oriented to SAML2 and not to Oauth2/OpenId. Can somebody help me? 回答1: At the moment you cannot create OAuth / OIDC applications through config files. You can add the service provider configs through config files. Problem is it does not populate the section "Inbound Authentication

问题 For test purpose I added a read-only LDAP look-up via the User Store Management menu at admin, selecting the option: org.wso2.carbon.user.core.ldap.ReadOnlyLDAPUserStoreManager After testing, I'm not able to remove this store entry at the Web console doing a "Select All" and selecting the the "Delete" icon. The command confirms deletion of the store, but after a new lookup the entry is still present. It is currently set in a disabled state, as some details are yet missing in the LDAP setup.

问题 For test purpose I added a read-only LDAP look-up via the User Store Management menu at admin, selecting the option: org.wso2.carbon.user.core.ldap.ReadOnlyLDAPUserStoreManager After testing, I'm not able to remove this store entry at the Web console doing a "Select All" and selecting the the "Delete" icon. The command confirms deletion of the store, but after a new lookup the entry is still present. It is currently set in a disabled state, as some details are yet missing in the LDAP setup.

问题 When using the WSO2 AM via the Store it is possible to set a Validity Time, so that the access token expire time can be increased/decreased. Is it possible to set the Validity Time via cURL when generating a new token? E.g. Normal token generation command: curl -k -d "grant_type=client_credentials" -H "Authorization: Basic userToken, Content-Type: application/x-www-form-urlencoded" localhost:8243/token {"scope":"am_application_scope default","token_type":"bearer","expires_in":1367,"access

问题 I created my own dialect using the manaement console Configure-->Claim Management. After doing this, I wanted to configure my Service Provider to be associated with these claims, so I edited my SP and went to the Claim Configuration section. The issue I am running into is the only Local Claim claims which show up are the default wso2 ones. So you only ever see ones starting with http://wso2.org/claims/. With that said, I don't believe choosing Define Custom Claim Dialect is an appropriate

问题 I am trying to implement the use case https://docs.wso2.com/display/EI650/Using+the+Gmail+Connector but in my case I am applying the gmail connector in out sequence but while exporting the .car file it is failing with error "error while extracting Synapse Library : gmail-connector-3.0.8.zip" I have tried adding the gmail connector in console but it is not reflecting yet, also tried restarting the server and redeploying several times but no luck here. Here is the full image of my project.

问题 I want to get access token without submiting Base64(client_id:client_secret) in the request. I just want to submit the client_id and username and password (Password Grant Type) : public passoword grant type It's called public scheme by IBM. Please quiclky skim through this likn. What I like is to never send the client_secret in an access token request. The image below illustrate it (still IBM). The problem is that WSO2 APIM requests to obtain access token ALWAYS include the Base64(client_id