This release can be downloaded from
"http://dist.wso2.org/products/commons/usermanager/0.1/"
Features of User Manager 0.1
============================
* User Management usig "org.wso2.usermanager.readwrite.DefaultRealm".
1) Add/edit/delete users
2) Add/edit/delete rolels
3) Manage users and roles
4) Manage user and role authorizations
* Plugin to Existing user stores
1) org.wso2.usermanager.custom.jdbc.JDBCRealm - This can connect to existing RDBMS user stores via a JDBC driver and authenticate users. It can retrieve user properties from the users table. This is tested using MySQL and Derby database drivers.
2) org.wso2.usermanager.custom.ldap.LDAPRealm - This can connect to existing LDAP server and authenticate users and retrieve user attributes. This is tested using open ldap.
3) org.wso2.usermanager.custom.acegi.AcegiRealm - Can perform authentication provided the bean mapping for AuthenticationProvider.
* A web app to perform user verification using Emails
This consist of 3 jsp files and a single class. Extract the webapp and integrate register.jsp, signon.jsp and validate.jsp to your application. Add the WEB-INF/lib files and classes directory to your war file or classpath.
For more information please refer
"http://wso2.org/repos/wso2/trunk/commons/usermanager/distribution/README"
Friday, September 21, 2007
Wednesday, September 19, 2007
Managing users in your applications
At www.wso2.org we are working on a bunch of projects and all of them require user management at various levels. With WSO2 usermanager we are trying to come up with a library that will let the developers handle user authentication and authorization in applications in a homogeneous manner. This is code is available under Apache licence.
The usermanager's main point of entry into a user store (Database/LDAP directory) is a org.wso2.usermanager.Realm implementation. The next release of the usermanager will provide two such implementation for LDAP and JDBC. With a org.wso2.usermanager.Realm the application developer will be able to query the user store for tasks such as authentication, authorization and to obtain properties with respect to a certain user.
The usermanager's main point of entry into a user store (Database/LDAP directory) is a org.wso2.usermanager.Realm implementation. The next release of the usermanager will provide two such implementation for LDAP and JDBC. With a org.wso2.usermanager.Realm the application developer will be able to query the user store for tasks such as authentication, authorization and to obtain properties with respect to a certain user.
Monday, September 17, 2007
Sunday, September 16, 2007
Keystore Explorer
Here's a simple tool to explore contents of a keystore.
Source code is available here :
https://wso2.org/repos/wso2/people/ruchith/kse
Source code is available here :
https://wso2.org/repos/wso2/people/ruchith/kse
Thursday, September 06, 2007
Apache Rampart 1.3 Released
This is the 1.3 release of Apache Rampart.
Apache Rampart 1.3 is a toolkit that provides implementations of the WS-Sec* specifications for Apache Axis2 1.3, based on Apache WSS4J 1.5.3 and the Apache AXIOM-DOOM 1.2.5 implementations.
You can download the releases from:
http://www.apache.org/dyn/closer.cgi/ws/rampart/1_3
There are two main Apache Axis2 modules provided with this release.
* rampart-1.3.mar
This provides support for WS-Security and WS-SecureConversation
features.
* rahas-1.3.mar
This module provides the necessary components to enable SecurityTokenService functionality on a service.
Apache Rampart 1.3 uses a configuration model based on WS-Policy and WS-Security Policy. It is important to note that the Apache Rampart 1.0 style configuration is also available even though being marked as deprecated.
Apache Rampart 1.3 can be successfully used with the next Apache Sandesha2 release targeted towards Apache Axis2 1.3 to configure WS-SecureConversation + WS-ReliableMessaging scenarios.
The rampart module was successfully tested for interoperability with other WS-Security implementations.
WS - Sec* specifications supported by Apache Rampart are as follows:
* WS - Security 1.0
* WS - Secure Conversation - February 2005
* WS - Security Policy - 1.1 - July 2005
* WS - Trust - February 2005
* WS - Trust - WS-SX spec - EXPERIMENTAL
Thank you for using Apache Rampart.
Apache Rampart team
Apache Rampart 1.3 is a toolkit that provides implementations of the WS-Sec* specifications for Apache Axis2 1.3, based on Apache WSS4J 1.5.3 and the Apache AXIOM-DOOM 1.2.5 implementations.
You can download the releases from:
http://www.apache.org/dyn/closer.cgi/ws/rampart/1_3
There are two main Apache Axis2 modules provided with this release.
* rampart-1.3.mar
This provides support for WS-Security and WS-SecureConversation
features.
* rahas-1.3.mar
This module provides the necessary components to enable SecurityTokenService functionality on a service.
Apache Rampart 1.3 uses a configuration model based on WS-Policy and WS-Security Policy. It is important to note that the Apache Rampart 1.0 style configuration is also available even though being marked as deprecated.
Apache Rampart 1.3 can be successfully used with the next Apache Sandesha2 release targeted towards Apache Axis2 1.3 to configure WS-SecureConversation + WS-ReliableMessaging scenarios.
The rampart module was successfully tested for interoperability with other WS-Security implementations.
WS - Sec* specifications supported by Apache Rampart are as follows:
* WS - Security 1.0
* WS - Secure Conversation - February 2005
* WS - Security Policy - 1.1 - July 2005
* WS - Trust - February 2005
* WS - Trust - WS-SX spec - EXPERIMENTAL
Thank you for using Apache Rampart.
Apache Rampart team
Apache WSS4J 1.5.3 Released
Apache WSS4J Team is happy to announce the WSS4J-1.5.3 release.
Apache WSS4J is an implementation of the OASIS Web Services Security (WS-Security) from OASIS Web Services Security TC. WSS4J is a Java library that can be used to sign and verify SOAP Messages with WS-Security information.
You can download the releases from:
http://www.apache.org/dyn/closer.cgi/ws/wss4j/1_5_3
Apart from the binary and source distributions, we have an additional ZIP file that contains other required JAR files to install and run WSS4J.
Please refer to the *readme.* files in the distribution for further information regarding implemented features, additional information, links to the Wiki pages, etc.
Enjoy !
The WSS4J team
Apache WSS4J is an implementation of the OASIS Web Services Security (WS-Security) from OASIS Web Services Security TC. WSS4J is a Java library that can be used to sign and verify SOAP Messages with WS-Security information.
You can download the releases from:
http://www.apache.org/dyn/closer.cgi/ws/wss4j/1_5_3
Apart from the binary and source distributions, we have an additional ZIP file that contains other required JAR files to install and run WSS4J.
Please refer to the *readme.* files in the distribution for further information regarding implemented features, additional information, links to the Wiki pages, etc.
Enjoy !
The WSS4J team
Subscribe to:
Posts (Atom)