Return-Path: Delivered-To: apmail-cocoon-users-archive@www.apache.org Received: (qmail 67807 invoked from network); 4 Apr 2005 14:50:31 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 4 Apr 2005 14:50:31 -0000 Received: (qmail 71533 invoked by uid 500); 4 Apr 2005 14:50:23 -0000 Delivered-To: apmail-cocoon-users-archive@cocoon.apache.org Received: (qmail 71492 invoked by uid 500); 4 Apr 2005 14:50:23 -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 71476 invoked by uid 99); 4 Apr 2005 14:50:23 -0000 X-ASF-Spam-Status: No, hits=0.4 required=10.0 tests=DNS_FROM_RFC_ABUSE,RCVD_BY_IP,SPF_HELO_PASS,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (hermes.apache.org: domain of elad.messing@gmail.com designates 64.233.184.193 as permitted sender) Received: from wproxy.gmail.com (HELO wproxy.gmail.com) (64.233.184.193) by apache.org (qpsmtpd/0.28) with ESMTP; Mon, 04 Apr 2005 07:50:21 -0700 Received: by wproxy.gmail.com with SMTP id 58so1456715wri for ; Mon, 04 Apr 2005 07:50:19 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:from:to:subject:date:mime-version:content-type:content-transfer-encoding:x-mailer:in-reply-to:thread-index:x-mimeole:message-id; b=ISWtb0yLQICYqsniqEAk+WMVAC93FFfrjdW+WecIJo7kisnoOyfztHw1lwGafgB2f90dyIG0Mwq+O7zdp6xCCeK8AQGaz+xsR1IboRtmO6VvrHB1l5ELmt4jrN0f2WMyPFnxrDIdxbQ3+XH2wkvUCSAjpmeCfR/dA/VfV7yqqJE= Received: by 10.54.25.74 with SMTP id 74mr98629wry; Mon, 04 Apr 2005 07:50:19 -0700 (PDT) Received: from h658 ([212.126.215.53]) by mx.gmail.com with ESMTP id g2sm900915wra.2005.04.04.07.50.18; Mon, 04 Apr 2005 07:50:19 -0700 (PDT) From: "Elad Messing" To: Subject: AW: Authentication and ROLES Date: Mon, 4 Apr 2005 16:49:45 +0200 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable X-Mailer: Microsoft Office Outlook, Build 11.0.5510 In-Reply-To: Thread-Index: AcU5IrBVRQpZtuBqSVaEfSLIEZ1MjwAAhHtA X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180 Message-ID: <4251542a.5dcb22f8.1aae.1c08@mx.gmail.com> X-Virus-Checked: Checked X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N I was just reading through the "Authentication Framework" documents, so = it is fresh in my head :) Have a look here : http://cocoon.apache.org/2.1/developing/webapps/authentication.html#Using= +a+ URI+as+the+authentication+resource The "role" is part of the data that could be added to as the "login" response. You can use this info when authorizing (after the authentication comes = the authorization). Hope this helps... Elad -----Urspr=FCngliche Nachricht----- Von: news [mailto:news@sea.gmane.org] Im Auftrag von Jorg Heymans Gesendet: Montag, 4. April 2005 16:28 An: users@cocoon.apache.org Betreff: Re: Authentication and ROLES This should be doable if you write your own authenticator. I don't know = if it's available off the shelve. Have a look at implementing the = Authenticator interface. Jakub Kaniewski wrote: > Is there possible to authenticate one pipeline, only when user have a=20 > certain ROLE (ie. admin). >=20 >=20 >=20 > J.K. --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscribe@cocoon.apache.org For additional commands, e-mail: users-help@cocoon.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscribe@cocoon.apache.org For additional commands, e-mail: users-help@cocoon.apache.org