Return-Path: X-Original-To: apmail-esme-dev-archive@www.apache.org Delivered-To: apmail-esme-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id D4BB99E30 for ; Thu, 29 Sep 2011 18:16:07 +0000 (UTC) Received: (qmail 91978 invoked by uid 500); 29 Sep 2011 18:16:07 -0000 Delivered-To: apmail-esme-dev-archive@esme.apache.org Received: (qmail 91945 invoked by uid 500); 29 Sep 2011 18:16:07 -0000 Mailing-List: contact dev-help@esme.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@esme.apache.org Delivered-To: mailing list dev@esme.apache.org Received: (qmail 91936 invoked by uid 99); 29 Sep 2011 18:16:07 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 29 Sep 2011 18:16:07 +0000 X-ASF-Spam-Status: No, hits=-2000.5 required=5.0 tests=ALL_TRUSTED,RP_MATCHES_RCVD X-Spam-Check-By: apache.org Received: from [140.211.11.116] (HELO hel.zones.apache.org) (140.211.11.116) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 29 Sep 2011 18:16:06 +0000 Received: from hel.zones.apache.org (hel.zones.apache.org [140.211.11.116]) by hel.zones.apache.org (Postfix) with ESMTP id 7BD262A0BF4 for ; Thu, 29 Sep 2011 18:15:45 +0000 (UTC) Date: Thu, 29 Sep 2011 18:15:45 +0000 (UTC) From: "Jack Park (Created) (JIRA)" To: dev@esme.apache.org Message-ID: <527291327.8455.1317320145509.JavaMail.tomcat@hel.zones.apache.org> Subject: [jira] [Created] (ESME-366) Consider adding Super-user functions MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 Consider adding Super-user functions ------------------------------------ Key: ESME-366 URL: https://issues.apache.org/jira/browse/ESME-366 Project: Enterprise Social Messaging Environment (ESME) Issue Type: New Feature Components: Server Affects Versions: 1.4 Environment: Any Reporter: Jack Park I left priority "Major", but that's an interpretation of the need for super-user functions, say, an Admin online page with features, as suggested here. 1- ability to "moderate" messages, particularly if any message becomes a liability to the site's admins. 2- ability to deal with users: boot/ban them (MediaWiki offers this), promote them to different roles 3- (my favorite) create Invitation Lists, say, of emails that are allowed to sign up -- useful for portals which are exposed but not intended for general public access or participation 4- other functions I didn't think of In my own work, I add a function in boot.scala that creates a default super-user based on credentials specified in the config properties. Perhaps that can be added to ESME as well. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira