Return-Path: Delivered-To: apmail-jackrabbit-dev-archive@www.apache.org Received: (qmail 56918 invoked from network); 25 Jul 2006 15:57:47 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 25 Jul 2006 15:57:47 -0000 Received: (qmail 36419 invoked by uid 500); 25 Jul 2006 15:57:46 -0000 Delivered-To: apmail-jackrabbit-dev-archive@jackrabbit.apache.org Received: (qmail 36387 invoked by uid 500); 25 Jul 2006 15:57:45 -0000 Mailing-List: contact dev-help@jackrabbit.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@jackrabbit.apache.org Delivered-To: mailing list dev@jackrabbit.apache.org Received: (qmail 36378 invoked by uid 99); 25 Jul 2006 15:57:45 -0000 Received: from asf.osuosl.org (HELO asf.osuosl.org) (140.211.166.49) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 25 Jul 2006 08:57:45 -0700 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests= X-Spam-Check-By: apache.org Received: from [209.237.227.198] (HELO brutus.apache.org) (209.237.227.198) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 25 Jul 2006 08:57:45 -0700 Received: from brutus (localhost [127.0.0.1]) by brutus.apache.org (Postfix) with ESMTP id 4236C7142B7 for ; Tue, 25 Jul 2006 15:55:20 +0000 (GMT) Message-ID: <31489138.1153842920268.JavaMail.jira@brutus> Date: Tue, 25 Jul 2006 08:55:20 -0700 (PDT) From: "Michael Bletzinger (JIRA)" To: dev@jackrabbit.apache.org Subject: [jira] Commented: (JCR-153) Improved JAAS access control MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N [ http://issues.apache.org/jira/browse/JCR-153?page=comments#action_12423376 ] Michael Bletzinger commented on JCR-153: ---------------------------------------- Hi, I was wondering if anyone has done something with this lately. The group I am working for is moving their application from jakarta-slide to jackrabbit. However they need WebDAV style access control support from the content repository. It seems this JCR is addressing this need. I found a thread here: http://mail-archives.apache.org/mod_mbox/jackrabbit-dev/200607.mbox/%3c44A83473.7000506@pobox.com%3e which discusses a possible implementation. The thread references an earlier discussion that I do not have access to. I have been given about two months to "move this issue forward". Please let me know if there is any way I can contribute to get this feature implemented in Jackrabbit. Suggestions pointing to other possible solutions would also be appreciated. Thanks Michael Bletzinger > Improved JAAS access control > ---------------------------- > > Key: JCR-153 > URL: http://issues.apache.org/jira/browse/JCR-153 > Project: Jackrabbit > Issue Type: Improvement > Components: security > Reporter: Jukka Zitting > Fix For: 1.1 > > > Fix the @todo entries in o.a.j.security.SimpleAccessManager to have a more fine-grained JAAS-based access control as the default Jackrabbit access control mechanism. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira