wso2

I am using the Identity Server 4.1.0 and also I am running an ApacheDS within the Apache Directory Studio. So what I want now is connect my IS to the external LDAP. IS is connecting fine to the ldap, only it throws errors because there are attribute-definitions missing. At least that is my interpretation of the stacktrace. I saw that other people tried it too: WSO2 external ldap not working But my error is different. Also I see how in this blog it is explained well how to use the Directory Studio, but it seems it is all running on the embedded LDAP of the IS: http://www.soasecurity.org/2012/11

How do I invoke a HTTPS endpoint from WSO2 ESB. My web service deployed on weblogic server is secured with policy Wssp1.2-2007-Https-UsernameToken-Plain.xml and the SOAP address specified in WSDL is https://172.16.91.21:7102/WLSAMLPack_62_64/CustomAsTAPIOnBuildingSAMLService When I try to create an endpoint from WSO2 esb and access it, it throws following error: [2012-08-29 11:43:49,769] ERROR - ClientHandler I/O error : General SSLEngine problem For : 172.16.91.21:7102 For Request : Axis2Request [Message ID : urn:uuid:59ebea16-dcb0-4b25-8074-b78605e2ff55] [Status Completed : false] [Status

I want to send a request over TCP transport to a proxy service, when use this code to send my soap xml Socket clientSocket = new Socket("host", port); DataOutputStream outToServer = new DataOutputStream(clientSocket.getOutputStream()); outToServer.writeBytes("soap xml instance"); clientSocket.close(); it works fine and my business is continues. But when i send two xml without closing the socket like this: Socket clientSocket = new Socket("host", port); DataOutputStream outToServer = new DataOutputStream(clientSocket.getOutputStream()); outToServer.writeBytes("soap xml instance"); outToServer

Maybe my understanding is wrong, please advice. Requirement: (1) user A, and user B wanna to access a web service SayHello. (2) only user A has permission. (3) SayHello web service simply return a string "hello" Previously: (1) To invoke SayHello, create a client according to SayHello?wsdl. -- Success (2) Create a proxy service SayHelloProxyService through ESB, host this proxy service to SayHello service, create a client according to SayHelloProxyService?wsdl. --Success Now: Add Identity Server inside, only give user A access permission, something like the following diagram : Question : for

AXIS2Server packed with ESB 4.9.0 doesn't start while it works fine 4.8.0.. .any help Hi, I'm running ESB 4.9.0 on Win 7 OS 64-it. Let's say my esb is available at following location D:\wso2esb\samples\axis2Server As per instructions to run samples, I'm able to successfully build sample apps using ant but axis2 server doesn't start at all. It prints following on CMD when i execute axis2server.bat. Am i missing something? ========================================================= Microsoft Windows [Version 6.1.7601] Copyright (c) 2009 Microsoft Corporation. All rights reserved. C:\Users\kashif

I am writing a REST API to be consumed by our internal applications. I need to login and logout users of the identity server using code grant via http requests presentation I need to know how to call the following endpoints: /authorize (invoked from server-side) /accesstoken (invoked from server-side) /login /logout CASE: Our company has many applications. I want one point of authentication which will happen in their company-x account like how you only need to login to atlassian account to access jira and confluence cloud. The REST API I'm working is for our front-end developers (as of now).

While trying out the new version of WSO2 Identity Server 5.1.0 I'm having problems returning claims in the SAML response. While this worked in WSO2 IS 5.0.0 SP1. I've mapped the required claims and added them to my SP, also I configured the SP to always return the user attributes. I've configured the SP claim mapping: My SAML configuration: Any help is greatly appreciated. I'm getting the feeling this might be a bug. EDIT: In WSO2 5.1.0 it is required to add the Attribute Consuming Service Index to the SAML Request. In WSO2 5.0.0 SP1 it worked even without setting this value in the SAML

Is it possible to hide tenant stores, so the they aren't visible in the public store, but only by their direct tenant specific store URL (like: https://api.mydomain.com/store/?tenant=mycustomer.com )? Background info: All our customers get their own tenant in the WSO2 API Manager. When an anonymous/unauthenticated visitor opens the public store ( https://api.mydomain.com/store ) he/she will see all tenant stores and their domain names. So it isn't really hard to discover the names of all our customers. This is undesirable. I know that the public store is supposed to promote public API's, but

I have installed the API manager 1.6.0 and got API Manager running as well. However the problem is IP address shown within store is the private IP of the server. Private IP is accessed via a VPN. Below is the URL which is shown in the store as Production and Sandbox URLs, http://192.168.6.162:8280/railway/2.0 For 192.168.6.162 I have assigned a public IP which is 103.11.35.xx and assigned a domain my-domain-name as well. What I would like to see is as below, http://my-domain-name/railway/2.0 How can I configure API Manager to show the domain name instead of an IP address with a port? You can