Return-Path: Delivered-To: apmail-geronimo-dev-archive@www.apache.org Received: (qmail 69292 invoked from network); 17 Oct 2006 18:37:34 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 17 Oct 2006 18:37:34 -0000 Received: (qmail 19510 invoked by uid 500); 17 Oct 2006 18:37:30 -0000 Delivered-To: apmail-geronimo-dev-archive@geronimo.apache.org Received: (qmail 19481 invoked by uid 500); 17 Oct 2006 18:37:29 -0000 Mailing-List: contact dev-help@geronimo.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: List-Post: Reply-To: dev@geronimo.apache.org List-Id: Delivered-To: mailing list dev@geronimo.apache.org Received: (qmail 19412 invoked by uid 99); 17 Oct 2006 18:37:29 -0000 Received: from asf.osuosl.org (HELO asf.osuosl.org) (140.211.166.49) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 17 Oct 2006 11:37:29 -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, 17 Oct 2006 11:37:28 -0700 Received: from brutus (localhost [127.0.0.1]) by brutus.apache.org (Postfix) with ESMTP id A9F277141D1 for ; Tue, 17 Oct 2006 11:36:36 -0700 (PDT) Message-ID: <13577644.1161110196693.JavaMail.jira@brutus> Date: Tue, 17 Oct 2006 11:36:36 -0700 (PDT) From: "Vamsavardhana Reddy (JIRA)" To: dev@geronimo.apache.org Subject: [jira] Commented: (GERONIMO-2413) Add a Certification Authority (CA) portlet to Geronimo console In-Reply-To: <20761258.1158635542272.JavaMail.jira@brutus> 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/GERONIMO-2413?page=comments#action_12443025 ] Vamsavardhana Reddy commented on GERONIMO-2413: ----------------------------------------------- How do you remove/edit CA info once configured? During the setup, CA (let me call it Geronimo CA) uses a self-signed certificate. If Geronimo CA decides to get certified by another CA, Geronimo CA can import its certificate into 'ca-keystore' using the keystore portlet. If Geronimo CA's certificate changes, it should be published again using the "Publish CA Certificate" link in CA Portlet. > Add a Certification Authority (CA) portlet to Geronimo console > -------------------------------------------------------------- > > Key: GERONIMO-2413 > URL: http://issues.apache.org/jira/browse/GERONIMO-2413 > Project: Geronimo > Issue Type: New Feature > Security Level: public(Regular issues) > Components: console, security > Reporter: Vamsavardhana Reddy > Fix For: 1.2, 1.x > > Attachments: 02.ca-initialization-enter-details.JPG, 07.issue-certificate-show-csr-details.JPG, 09.issue-certificate-successful.JPG, GERONIMO-2413-revised.patch, GERONIMO-2413-v1.2.patch, GERONIMO-2413.patch, GeronimoCA.zip > > > A Certification Authority portlet will be very useful. A full fledged CA may be a long way to go. But what ever minimum function is required to process CSR's etc. is not hard and the users can issue their own digital certificates instead of getting trial certificates from some CA. -- 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