Mailing-List: contact user-help@roller.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@roller.apache.org
Received-SPF: pass (athena.apache.org: domain of snoopdave@gmail.com
 designates 209.85.132.240 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=beta;
        h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
        b=biKoFOUBMbyGU0bRhQKeIe0rGf5XAuy0LI7O4JqAi0Euwbrg0OIFXaalcuiuhkM/DJqKpwtAtrjcjbituBrhvEVRRQihvyLDrBPM2+dSlhwKVgBOANyb4uFR+2FpGZ39fbDjZhE+EMmDw2ZmTMs9q4UcwaSet5zqPTWPjODpANE=
Message-ID: <8fb9ac720708230610s1a8fe932l9eb10784b7a57a90@mail.gmail.com>
Date: Thu, 23 Aug 2007 09:10:16 -0400
From: Dave <snoopdave@gmail.com>
To: user@roller.apache.org
Subject: Re: integrating roller user management with a portal user management
In-Reply-To: <CD71A727363F154A92719FB8779EE03302FE63@neon.ALLOT.LOCAL>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <CD71A727363F154A92719FB8779EE03302FE45@neon.ALLOT.LOCAL>
	 <8fb9ac720708200721q67749726yfcf7d6aaa7c4bc19@mail.gmail.com>
	 <CD71A727363F154A92719FB8779EE03302FE63@neon.ALLOT.LOCAL>

On 8/23/07, Guy Katz <gkatz@allot.com> wrote:
> RAP was exactly what I needed.
> Took me a while to get the hang of dealing with it but once I got it, it
> was easy (With the help of the self-marshaling objects in the SDK).
>
> The documentation states that it is not to be used in production. Is
> this only for security reasons?

Originally, we marked it as experimental because it was loosely based
on Atom protocol and Atom protocol was not final.

Personally, I would like to see RAP rewritten so that it conforms to
Atom protocol.

> I can add a filter to roller to allow only the local machine to send the
> XML as my roller and my portal will reside on the same tomcat. Do you
> think its sufficient?

That sounds like a good idea. If you are going to run RAP on separate
machine, I'd recommend using HTTPS so that passwords are not sent in
the clear.

- Dave


> -----Original Message-----
> From: Dave [mailto:snoopdave@gmail.com]
> Sent: Monday, August 20, 2007 5:22 PM
> To: user@roller.apache.org
> Subject: Re: integrating roller user management with a portal user
> management
>
> On 8/20/07, Guy Katz <gkatz@allot.com> wrote:
> > I want to integrate roller inside a portal where user management is
> done by the portal.
> >
> > The user registration code resides in the portal such that when a user
> > decides to register for the portal, a new user is created for it both
> in
> > the user DB in the portal and then in roller as well.
> >
> > Is there a nice way to integrate with roller to achieve this? I can
> > always just do SQL to the DB but I'd rather use some kind of a roller
> > mechanism or classes. I can probably have access to Roller's servlet
> > context from my portal application (deployed on the same tomcat) by
> > configuring roller 'crossContext=true' in tomcat.
> >
> > Are there any objects (such as user manager) in the roller servlet
> > context that I can retrieve and use in order to trigger a 'new user'
> > command?
> >
> > What are the integration methods that are available as an option in
> such
> > a situation?
>
> Let's see. You could:
>
> - Use the Roller Admin Protocol (RAP) to provision a new Roller user
> everytime one is added to the Portal. http://tinyurl.com/3amanz
>
> - Write a new JSP page for Roller that will respond to (authenticated)
> requests to create new users in Roller. The JSP page would call the
> UserManager.addUser() method. Then call that page from your Portal
> server.
>
> - Wait for Roller 4.1's new extensible user management, then plugin
> your own user manager. http://tinyurl.com/28br55
>
> Hope that helps.
>
> - Dave
>