Adding InfoCard login to a J2EE Web Application

This article by Dimuthu, explains how one can set up information card logins with J2EE web applications using WSO2 Identity Solution 1.0 java relying party servlet filter component.

WSO2 Registry 0.1 Released

WSO2 Registry enables you to store, catalog, index and manage your enterprise meta data in a simple, scalable and easy-to-use model. It is designed around community concepts such as tags, comments, ratings, users and roles. Think of the registry as a structured wiki designed to help you manage your meta-data in a simple business-friendly system.

In addition, the registry allows you to store more unstructured data such as Word documents, Excel spreadsheets and text formats. Using these approaches, you can build a catalog of enterprise information ranging from services, service descriptions to employee data and on going projects.

WSO2 Registry can be deployed in Application Servers and access using the Web UI or the APP interface. It can also be used as a Java library inside other Java programs as a resource store with all community features and versioning.

WSO2 Registry is released under the Apache License v2.0


Features List
- Storing and managing resources and collections
- Tagging, commenting and rating resources
- Managing users and roles
- Authentication and authorization
- Resource / collection versioning
- Tag based search
- Advanced search
- Activity log and filtering support for the activity logs
- APP based Remote Registry
- Media type handling support (experimental)
- Web based user interface with Web 2.0 look and feel

Release can be download from http://wso2.org/downloads/registry

OpenId Information Cards: CardSpace with a different token type?

Prabath, who is working on integrating OpenID with WSO2 Identity Solution has made some interesting notes about OpenID and CardSpace.

I certainly do agree with his points and I also fail to see the real value addition that OpenID information cards brings in when compared to CardSpace. Isn't it same old CardSpace with a different token type?

By the way ... we hope to have OpenID support integrated into our Identity Provider in the next release of the Identity Solution. So... stay tuned! :-)

WSO2 Identity Solution 1.0 is now available

We released the WSO2 Identity Solution last week with an Identity Provider and a set of relying party components.

The identity provider component supports issuance of information cards and tokens defined by Microsoft CardSpace specifications. Some of the main features are :

• Simple management console


• Ability to connect to custom user stores (LDAP/Microsoft ActiveDirectory, JDBC)


• Built in user store


• Support for the CardSpace default claim set


• Support for custom claim dialects and claims types


• Statistics/reporting/audit trail


• Ability to revoke information cards


• Issues information cards based on username-token credential and self issued credential

The relying party components includes an Apache2 HTTPD module (mod_cspace) and a Java servlet filter component. mod_cspace has useful features such as ability to enforce CardSpace authentication on static web content. Extensions for Drupal, MediaWiki are also available that can be easily configured with mod_cspace.

Documentation on setting up and using the identity provider and other relying party components are available at http://wso2.org/project/solutions/identity/1.0/docs/index.html