wso2

问题 I have problems getting work "SAML2 Bearer Assertion profile for Oauth" within WSO2 API Manager. I'm trying to apply "Johann's Wall" How-to on API Manager (ver. 1.5) but running in the following error. [2013-11-08 17:44:35,930] DEBUG - SAML2BearerGrantTypeHandler SAML Assertion Audience Restriction validation failed [2013-11-08 17:44:36,024] DEBUG - AccessTokenIssuer Invalid Grant provided by the client, id=enfKWsilmCxdIwhYiINcoA2JKwka, user-name=admin to application=MyFlowChart [2013-11-08

问题 i am getting the data from mobile client they are sending data in JSON as well as sending some values as HEADER to WSO2ESB i am getting normal values using this property <property name="asset" expression="//asset/text()" scope="default"/> but how can i get HEADER in my ESB i am using this property its not not working <property name="username" expression="get-property('transport', 'Accept')"/> how it will work will you revert me as soon as Thanks in advance 回答1: if what you are trying to

问题 I want to externalize the hostname and port number in HTTP endpoint, so I am trying to pass the hostname and port number in JVM argument while starting the ESB. Using script/class mediator, I can get it from system properties and put it in message context. Then using property mediator, I can access and log the value of it. Till this point, I don't have any issue but when I try to use this value to replace in the HTTP endpoint as below; it doesn't work. Actual ESB Synapse API Config: <api

问题 I'm referring to the following article: http://wso2.org/library/articles/2010/07/saml2-web-browser-based-sso-wso2-identity-server This example works with identity server 4.0.0 but NOT with identity server 4.1.0... With 4.1.0 - the SAML response is returned, but the relying party application throws an exception when it is trying to deserialize the message. Could this sample be updated to work with the later version of IS? Here's the stack trace of the relying party application: SEVERE: Servlet

问题 ERROR: Enrich mediator Invalid Object type to be inserted into message body when trying to enrich the message, here is the proxy configuration: <proxy xmlns="http://ws.apache.org/ns/synapse" name="Database" transports="https,http" statistics="disable" trace="disable" startOnLoad="true"> <target> <inSequence> <dblookup> <connection> <pool> <password>1234</password> <user>root</user> <url>jdbc:mysql://localhost:3306/new_db</url> <driver>com.mysql.jdbc.Driver</driver> </pool> </connection>

问题 I am trying to figure out how to implement session management in wso2 esb.So i have written a class mediator which generates session_ID that i want to store.For storing the session id I am using following code as: org.apache.axis2.context.ServiceContext serviceContext = org.apache.axis2.context.MessageContext .getCurrentMessageContext().getServiceContext(); serviceContext.setProperty("SessionIDGlobal", uuid); But while running it in my esb's proxy it throws null pointer exception at

问题 I'm evaluating WSO2 platform for further use. I appreciate a lot this platform's techinacl pillars. I see that links to Gadegt Server in WSO2 site redirect to User Engagement Server. Does it mean that Gadget Server will be closed and subsituted by User Engagement Server? Thanks a lot for your attention. Pino 回答1: Yes, WSO2 Gadget Server is deprecated now. That's why Gadget Server links are redirected to WSO2 User Engagement Server. WSO2 UES is a successor to Gadget Server. You can check out

问题 I developed a REST API in wso2esb 5.0.0 and I am facing some problems when client send a request that contains ã , ç or é for example, the first mediator on inSequence pipeline, Raise an error about Invalid UTF-8 middle byte . When we force charset of message in HTTP header as ISO-8859-1, works fine. But we need to work with UTF-8. Somebody already face this issue and could help me? Following the stack trace off error: TID[-1234] [ESB] [2017-07-04 15:12:26,738] ERROR {API_LOGGER.ResourceAPI}

问题 Is below possible using WSO2 IS? I have gone through different WSO2 blogs. They are nice pointer. Still I need to advised on this. Requirement- WSO2 Identity Server + Rest STS Client (without ESB) Users are managed on WSO2 Identity Server. STS Client use RestFul API to call WSO2 Identity Server's STS service for a) Get Security Token b)Validate Token c)cancel Issued Token d) renew Issued Token Retrieve user profile using a specific Security token. Reference: https://web.cci.emory.edu

问题 I'm trying out OAuth/OpenID with WSO2 Identity Server 5.1.0, but I'm having problems with returning the claims I need. I'm not sure if I'm misunderstanding how this should work... I'm using the default resident identity provider. The service provider has the claims configured like this: This only other configuration for this SP is inbound authentication with OAuth2. When I get an OAuth token for this service using the openid scope, the JWT received only has the subject field (email address in