Mailing-List: contact directory-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Apache Directory Developers List"
 <directory-dev@incubator.apache.org>
From: "Alex Karasulu" <aok123@bellsouth.net>
To: "'Apache Directory Developers List'" <directory-dev@incubator.apache.org>
Subject: RE: [vote] RMS - Realm Management System
Date: Wed, 7 Apr 2004 00:36:05 -0400
MIME-Version: 1.0
Content-Type: text/plain;
	charset="US-ASCII"
Content-Transfer-Encoding: 7bit
In-Reply-To: <20040407042917.THDZ1729.imf24aec.mail.bellsouth.net@franklin>
Thread-Index: AcQb+IVUrPgHPcpOSYuc4UvUv0FmAAAAK6EgABea2iAAAGDDcA==
Message-Id: <20040407043608.TIXI1729.imf24aec.mail.bellsouth.net@franklin>

Oh and just to give you all an update of the voters that chimed in
on the PPMC list here are the current votes:

Noel +1
Jeff +1
Robb +1
Me +1

Alex

> -----Original Message-----
> From: Alex Karasulu [mailto:aok123@bellsouth.net]
> Sent: Wednesday, April 07, 2004 12:29 AM
> To: 'Alex Karasulu'; 'Directory PPMC'
> Subject: [vote] RMS - Realm Management System
> 
> Hi,
> 
> This is a repost of the original RMS email which got kicked off
> somehow as vote on the PPMC list.  We just want to make sure
> everyone is considered before we close this vote and realized
> that it actually belongs on the dev list.
> 
> As most of you guys know some of us have been working on the Realm
> Management System (RMS) over at source forge here:
> 
> http://openrms.sourceforge.net
> 
> The crew is basically composed of a subset of us and the project uses the
> Apache Software License.
> 
> This is a very high level framework for storing and managing relatively
> static information within an application domain or realm in a directory.
> It can store user's, groups and application permissions as well as
> aspects of a user's profile that are unrelated to security.  Basically
> RMS is a place to centralize information that is shared and changes
> relatively infrequently.
> 
> The most obvious information it looks up is security information right
> now, namely authentication and authorization information.  It pluggable
> and modular with GUI tools for managing these aspects of applications
> within your operational environment.  In this respect it handles, at a
> high level, various identity management related tasks allowing for the
> centralization and federation of identity.
> 
> RMS is designed to sit on top of Janus and use any LDAP server.  In fact
> we are in the process of plugging in Janus under RMS to support various
> low level operations and we are finding a high degree of overlap.  We are
> also noticing that the RMS project fits more in line with our endeavors
> within the directory project.  It will also be able to use Janus and other
> API's to access static information stored perhaps in XML files.  The
> backing store will be completely pluggable.
> 
> Currently I will be commissioned to work on this project pretty
> aggressively for CitiStreet a CitiGroup company.  In the hopes of
> exploring the potential of using the code and having it synergize with our
> efforts within the directory project I went ahead and requested the
> submission of a Corporate CLA by CitiStreet and we have confirmation of it
> being faxed in.  This is a major feat btw to have such an entity be so
> accepting of us and open source.
> 
> I wanted to let you guys know about where things are with this project and
> how much it overlaps with our goals.  I would like to discuss its value
> here and whether or not it's worth taking a vote to bring it on instead of
> working separately on it.  In a way I think it is going to be an extension
> of Janus.
> 
> Alex
> 
>