Project: WSO2 Identity Server (WSO2 IS)

I am trying to deploy Identity Server 3.2.3 on IBM Websphere 8 according to http://wso2.org/library/knowledge-base/2011/02/running-wso2-carbon301-based-products-ibm-websphere-61 and information about the differences between 3.0.x and 3.2.3 i found in this email thread http://old.nabble.com/Testing-on-Websphere-to31564436.html#a31570416 . Unfortunately it is not working. Is there an updated how to for Websphere 8 and WSO2 IS 3.2.3? Best regards Klaus Sadowski

Hi, I just started looking into using IS. Do you have any recent tutorials/sample code on how to do user authentications? I found a few blog entries online: for example, http://blog.facilelogin.com/2010/05/managing-users-and-roles-with-wso2.html but the issue I have is the blog lists a number of dependency jars, yet I cannot find their equivalents in the latest IS binary distro (v3.2.3). Thanks. -- Y.

I see Identity Server has HTTP Digest Auth listed in the specification. How can I activate it to secure my web services?

I don't see STS feature in Strato's WSO2 Identity Server offering. is there any possibility to activate STS on Strato's WSO2 Identity Server like we have in standalone WSO2 Identity Server ? Thanks Sumanth

With the public cloud, how easy is it for us to change the number of instance we want to use? For example: can we decide to use 2 servers during daytime and 1 server night time? How does IS help link a web user to that client id? Does IS (LDAP) allow to store the client id along with the login information?

Case: I am trying to test local CXF Client (Grails webApp)  accessing Hosted Web Service on WSO2 ESB that has a security policy that require issued Token (SAML) from my local STS (WSO2 Identity Serve)

Environment

Hi, We are trying to setup multitenancy support to our wso2 IS server as mentioned in the wso2 developer blogs. We are able to login as admin, create tenants and activate them. But while trying to loging in to carbon as a tenant admin of an active tenant, we are getting the following error. DEBUG {org.wso2.carbon.activation.module.ActivationHandler} - Staring Activation Handler invocation.

Requesting identity information using the OpenID Attribute Exchange Mechanism i discovered the following problem. The WSO2 identity server looses the correlation to the FetchRequest attributes alias. When creating a FetchResponse in OpenIDAttributeExchange#setAttributeExchangeValues(FetchResponse, Map) the method FetchResponse#addAttribute(String, String) is used.