Return-Path: X-Original-To: apmail-incubator-bloodhound-dev-archive@minotaur.apache.org Delivered-To: apmail-incubator-bloodhound-dev-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id B3921EED9 for ; Tue, 22 Jan 2013 10:57:53 +0000 (UTC) Received: (qmail 13364 invoked by uid 500); 22 Jan 2013 10:57:53 -0000 Delivered-To: apmail-incubator-bloodhound-dev-archive@incubator.apache.org Received: (qmail 13304 invoked by uid 500); 22 Jan 2013 10:57:52 -0000 Mailing-List: contact bloodhound-dev-help@incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: bloodhound-dev@incubator.apache.org Delivered-To: mailing list bloodhound-dev@incubator.apache.org Received: (qmail 13259 invoked by uid 99); 22 Jan 2013 10:57:51 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 22 Jan 2013 10:57:51 +0000 X-ASF-Spam-Status: No, hits=2.2 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_NEUTRAL X-Spam-Check-By: apache.org Received-SPF: neutral (athena.apache.org: local policy) Received: from [209.85.219.48] (HELO mail-oa0-f48.google.com) (209.85.219.48) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 22 Jan 2013 10:57:40 +0000 Received: by mail-oa0-f48.google.com with SMTP id h2so7045229oag.21 for ; Tue, 22 Jan 2013 02:57:18 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:content-type:x-gm-message-state; bh=BF5xFit1J5mrCrsFJhK8Tv7H0d/PMi6Z0qEawHYpMVs=; b=FTNuGCEvLYffoEmqL343e5CxrN3b4G3n05Ea+JwZ9gI5BfXmfcywZAqqRlvmmpl0rR yIRkckPTCTaP8mK53jO4DZIX+y2hkThizaVrwzPqZkVKVn8ZSgJOH+p2M9Iv7zn0F3VW KlijEliMcJzc5eT51wCK+84kpsmQfxYe9OjcYIyJ/OOeD91Icme7ih7PKKIYUKLicxyi hn/vxeGEhFPWuA3q51DsLWTZl/kenq932x4ZlTz6d/t7NEzGuxQ7ukuiwE5gdyrM/J3u ypvjah2249l1Q4j12wFsLJnojdS44a47oBhWd3N67//vf3jI19YUCe0oZ9jp0myjcjkT Abuw== MIME-Version: 1.0 X-Received: by 10.182.54.102 with SMTP id i6mr16296612obp.67.1358852238673; Tue, 22 Jan 2013 02:57:18 -0800 (PST) Received: by 10.76.96.76 with HTTP; Tue, 22 Jan 2013 02:57:18 -0800 (PST) In-Reply-To: References: Date: Tue, 22 Jan 2013 11:57:18 +0100 Message-ID: Subject: Re: AccountManagerPlugin From: =?UTF-8?Q?Peter_Ko=C5=BEelj?= To: bloodhound-dev@incubator.apache.org Content-Type: multipart/alternative; boundary=14dae93a1145fd056004d3de7094 X-Gm-Message-State: ALoCoQlDwb2384+uUT/jwKaZnhWKplZSmyx4/68f7iSwnMOk+cDL1hGufidhAbtqGOR/bysfATKy X-Virus-Checked: Checked by ClamAV on apache.org --14dae93a1145fd056004d3de7094 Content-Type: text/plain; charset=ISO-8859-1 > For now, I just wanted to list some of the features that are on the table >> for upcoming releases, and give the Bloodhound community the chance to >> comment on what might be most important to tackle for upcoming releases. I >> will consider focusing my efforts according to whatever feedback I >> receive. >> The following is a list that I've loosely prioritized according to my >> current thinking: >> 1. #10747: Allow accounts to be created from the command line by >> implementing IAdminCommandProvider interface, and consider other commands >> to implement >> 2. #10002: Allow accounts to be manually locked >> 3. #1001: Implement an extensive XmlRpc interface >> 4. #3113: Implement more extensive password policy checks >> 5. Integrate the UserManagerPlugin (I've taken over maintenance of this >> plugin and will provide more info on what this plugin provides once I get >> more up to speed on the codebase). >> 6. #9947: Integrate functionality of FineGrainedPageAuthzEditorPlugin >> 7. Integrate the HtGroupsEditPlugin >> 8. #9943: Add group-based and preference-based configurable login page >> 9. Integrate the PermRedirectPlugin >> 10. Enhance the plugin's macros by integrating the UserStatsMacro and >> WikiStatsMacro. >> > > There is one thing that I am missing from this list that should probably > be number 1: Bloodhound multiproduct awareness > I must admit that I am not familiar enough with AccountManager plugin and > Trac's security model at the moment to form a proper feature request. > > I will look into both to get an idea what we want/need here. If it turns > out that BH requires some BH multiproduct specific changes to be useful to > us, do we have any idea how plugin author would see such a request? > > I had a look at the AccountMangerPlugin and if I did not miss something, plugin does not concern itself with permissions at all. Would that be correct? If this is in fact so, it is a good news to me as it means that no special support for multiproducts is required. --14dae93a1145fd056004d3de7094--