The PURSe portlets are a set of user and administrative portlets for interfacing with PURSe, the Portal-based User Registration System. From the PURSe website, PURSe is
a system for registering users of Web-based applications that use the Grid Security Infrastructure (based on PKI and X.509 certificates). PURSE coordinates the process of establishing Grid security certificates for new users when logging in to an application web site. Users who already have valid certificates can also easily register with the portal applications. By leveraging the MyProxy certificate repository, PURSe shields web application users from the complexities of X.509 certificate management, and enables rapid registration of users.
The PURSe portlets are JSR-168 compliant and are intended as a reuseable interface to PURSe to be used by JSR-168 compliant portal frameworks such as GridSphere, uPortal, Liferay, etc. These portlets are ideal for the Grid portal administrator who needs to provide a mechanism by which portal users can request and be granted Grid security credentials, without exposing portal users to the hassle of managing their credentials themselves.
To get started with using the PURSe portlets, read the PURSe Administrator's Guide for instructions on how to install PURSe and it's required software. Then check out the PURSe Portlets Administrator's Guide for information on how to deploy and configure the PURSe Portlets.
If you have questions, you can email Marcus Christie.
Tue July 24, 2007
Wed August 9, 2006
Wed May 31, 2006
An updated PURSe System Source Tarball is now available. This contains an updated cog-jglobus jar (necessary to compile the code) and the test code has been updated so that it now also compiles.
May 11, 2006
See the announcement for this release for more information. The following items are available for download as part of this release:
Nov 1, 2005
The following items are available for download as part of this release:
Updated Feb 16, 2006
Please note that the
supplied with this war file may not be appropriate for your
GridSphere installation. If you experience problems, use the
gridsphere-ui-tags.jar deployed in your GridSphere webapp