Return-Path: Delivered-To: apmail-geronimo-dev-archive@www.apache.org Received: (qmail 8329 invoked from network); 3 Jun 2009 07:00:24 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 3 Jun 2009 07:00:24 -0000 Received: (qmail 86782 invoked by uid 500); 3 Jun 2009 07:00:36 -0000 Delivered-To: apmail-geronimo-dev-archive@geronimo.apache.org Received: (qmail 86689 invoked by uid 500); 3 Jun 2009 07:00:35 -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 86681 invoked by uid 99); 3 Jun 2009 07:00:35 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 03 Jun 2009 07:00:35 +0000 X-ASF-Spam-Status: No, hits=-2000.0 required=10.0 tests=ALL_TRUSTED X-Spam-Check-By: apache.org Received: from [140.211.11.140] (HELO brutus.apache.org) (140.211.11.140) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 03 Jun 2009 07:00:33 +0000 Received: from brutus (localhost [127.0.0.1]) by brutus.apache.org (Postfix) with ESMTP id 3EE99234C055 for ; Wed, 3 Jun 2009 00:00:13 -0700 (PDT) Message-ID: <447473159.1244012413251.JavaMail.jira@brutus> Date: Wed, 3 Jun 2009 00:00:13 -0700 (PDT) From: "Ivan (JIRA)" To: dev@geronimo.apache.org Subject: [jira] Commented: (GERONIMO-4669) EJ B security does not work correctly when no permssion is set and the user does a login In-Reply-To: <53326082.1244009767488.JavaMail.jira@brutus> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 X-Virus-Checked: Checked by ClamAV on apache.org [ https://issues.apache.org/jira/browse/GERONIMO-4669?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12715841#action_12715841 ] Ivan commented on GERONIMO-4669: -------------------------------- >From my view, I would like to use the old way, even if no method permissions exist, a JACC Manager is also created, which will add all the method permissions to the exclude list. Maybe, to set the securityEnabled to false is also a good choice, but it may affect the invocation of getCallerPrincipal Any comment ? > EJ B security does not work correctly when no permssion is set and the user does a login > ---------------------------------------------------------------------------------------- > > Key: GERONIMO-4669 > URL: https://issues.apache.org/jira/browse/GERONIMO-4669 > Project: Geronimo > Issue Type: Bug > Security Level: public(Regular issues) > Components: OpenEJB > Affects Versions: 2.2 > Reporter: Ivan > Assignee: Ivan > Fix For: 2.2 > > > Currently, if in the ejb-jar.xml file, not method-permission exists, we will not create a JACC Manager. But the securityEnabled is always set to true, so while the user login in, then the access is denied. In the past versions, we always create a JACC Manager even if no method permisson is set, and in it, all the method invocation permissions are granted. This issue blocked some EJB TCK testcases, I think. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.