Return-Path: Delivered-To: apmail-cocoon-users-archive@www.apache.org Received: (qmail 65230 invoked from network); 24 Feb 2004 07:11:05 -0000 Received: from daedalus.apache.org (HELO mail.apache.org) (208.185.179.12) by minotaur-2.apache.org with SMTP; 24 Feb 2004 07:11:05 -0000 Received: (qmail 15252 invoked by uid 500); 24 Feb 2004 07:10:31 -0000 Delivered-To: apmail-cocoon-users-archive@cocoon.apache.org Received: (qmail 15225 invoked by uid 500); 24 Feb 2004 07:10:31 -0000 Mailing-List: contact users-help@cocoon.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: list-post: Reply-To: users@cocoon.apache.org Delivered-To: mailing list users@cocoon.apache.org Received: (qmail 15180 invoked from network); 24 Feb 2004 07:10:29 -0000 Received: from unknown (HELO smtp1.jouve.fr) (193.108.166.138) by daedalus.apache.org with SMTP; 24 Feb 2004 07:10:29 -0000 From: "Laurent Trillaud" To: , Subject: RE: User coplet access in new Portal Engine Date: Tue, 24 Feb 2004 08:09:48 +0100 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_00C5_01C3FAAD.9294FE30" X-Mailer: Microsoft Office Outlook, Build 11.0.5510 In-Reply-To: X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165 Thread-index: AcP6WIXONKokz2gHQKibgtLA9qmuvQATBPoA Message-Id: <20040224071039.7A2E611402@smtp.mayenne.jouve.fr> X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N X-Spam-Rating: minotaur-2.apache.org 1.6.2 0/1000/N ------=_NextPart_000_00C5_01C3FAAD.9294FE30 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Jeff It=92s pretty easy to do. Configure the role in the portal/resources/sunrise-user.xml, then create portal/layout/portal-[user|role]- files. The portal will match before user name, if not role name, if not got the portal.xml. For exemple: portal-user-anonymous.xml, portal-role-poweruser.xml, portal-role-admin.xml Laurent Trillaud =20 _____ =20 De : Jeff Davis [mailto:jedavis@firstam.com]=20 Envoy=E9 : lundi 23 f=E9vrier 2004 23:01 =C0 : users@cocoon.apache.org Objet : User coplet access in new Portal Engine =20 I=92m setting up a portal that requires role-based coplet access (i.e., = some coplets will appear for some users but others not). I know this is = probably supported, but I didn=92t see an example of it in the Portal sample that = comes with Cocoon 2.1.4. Does anyone have an samples of role-based coplet = security being applied? =20 Thanks so much, =20 jeff ------=_NextPart_000_00C5_01C3FAAD.9294FE30 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable

Jeff

It’s = pretty easy to do.

Configure the = role in the portal/resources/sunrise-user.xml, then create portal/layout/portal-[user|role]-<name> files.

The portal will = match before user name, if not role name, if not got the = portal.xml.

For exemple: = portal-user-anonymous.xml, portal-role-poweruser.xml, portal-role-admin.xml

Laurent = Trillaud

 

De : Jeff = Davis [mailto:jedavis@firstam.com]
Envoyé : = lundi 23 février 2004 23:01
À : = users@cocoon.apache.org
Objet : User coplet = access in new Portal Engine

 

I’m setting up a portal that requires role-based coplet access (i.e., some coplets will appear for some users = but others not). I know this is probably supported, but I didn’t see = an example of it in the Portal sample that comes with Cocoon 2.1.4. Does = anyone have an samples of role-based coplet security being = applied?

 

Thanks so much,

 

jeff

------=_NextPart_000_00C5_01C3FAAD.9294FE30--