Mailing-List: contact jetspeed-user-help@portals.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Jetspeed Users List" <jetspeed-user@portals.apache.org>
Received-SPF: pass (asf.osuosl.org: domain of aaronmevans@gmail.com designates
 66.249.92.192 as permitted sender)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws;
        s=beta; d=gmail.com;
        h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:references;
        b=gc46zfsTaCEgoRcmopqjg0iNOqfTNs8UVW1F3XC/BrO6um9wck1e4Q/Rp74Q3QEoyWFkOQz4fvb10w+JUFQga5K56BwFfxryPConvq5DsK/A+b0/IW1LPG9F/a8a1KRbSKRE/ipVu0uI6rJBVVFqR/zmpRg7gR2DRVZONjYWO48=
Message-ID: <e93a0aea0601250518n26047630y9f2696062570a286@mail.gmail.com>
Date: Wed, 25 Jan 2006 08:18:59 -0500
From: Aaron Evans <aaronmevans@gmail.com>
To: Jetspeed Users List <jetspeed-user@portals.apache.org>
Subject: Re: dev or user group question?
In-Reply-To: <3D68A9B9A8E58049A19EBD6D561A33050B1CEF@R2D2.CCGI.INTRA>
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_Part_48348_1304008.1138195139029"
References: <3D68A9B9A8E58049A19EBD6D561A33050B1CEF@R2D2.CCGI.INTRA>

------=_Part_48348_1304008.1138195139029
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline

This is relatively easy to do.

You just have to implement the following interfaces:

org.apache.jetspeed.security.spi.UserSecurityHandler
org.apache.jetspeed.security.spi.RoleSecurityHandler
org.apache.jetspeed.security.spi.GroupSecurityHandler
org.apache.jetspeed.security.spi.SecurityMappingHandler

And then change the configuration of the security-spi.atn.xml and
security-spi-atz.xml spring
assembly files to use your implementations.

Note that you don't necessarily need to implement all of the above, you
could for example
leave Group managment in jetspeed and not implement the GroupSecurityHandle=
r
and then
only override the methods in the default SecurityMappingHandler
implementation as it relates
to roles for authorization.

By looking at the default implementations and the LDAP authentication
implementation, I was
able to figure it out and have jetspeed use my custom implementations that
utilize my LDAP
schema for users, groups and roles.

HTH,
aaron

On 1/24/06, Garner Andrews <Garner@ccgi.net> wrote:
>
> We have our own security app that we've revealed with a web service.  We
> want to replace the Jetspeed2 authentication and authorization functions
> with our app.  Has anyone experimented with this at all yet?  Can you
> even swap out the internal portal maintenance users' security roles or
> do you have to use what's already there?  I'm really trying to gauge the
> level of effort this will take.  I've read everything I have found so
> far in the mail archives and in the other support areas and not found
> answers to these questions yet.  If I missed something, please don't
> hesitate to point me in the right direction.
>
> Thanks,
> Garner
>
> C. Garner Andrews
> Enterprise Architect
> CompuNet Consulting Group, Inc.
> +mailto:garner@ccgi.net
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: jetspeed-user-unsubscribe@portals.apache.org
> For additional commands, e-mail: jetspeed-user-help@portals.apache.org
>
>

------=_Part_48348_1304008.1138195139029--