Return-Path: X-Original-To: apmail-activemq-commits-archive@www.apache.org Delivered-To: apmail-activemq-commits-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 5E51E775D for ; Mon, 29 Aug 2011 07:48:18 +0000 (UTC) Received: (qmail 17012 invoked by uid 500); 29 Aug 2011 07:48:17 -0000 Delivered-To: apmail-activemq-commits-archive@activemq.apache.org Received: (qmail 16711 invoked by uid 500); 29 Aug 2011 07:48:05 -0000 Mailing-List: contact commits-help@activemq.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@activemq.apache.org Delivered-To: mailing list commits@activemq.apache.org Received: (qmail 16683 invoked by uid 99); 29 Aug 2011 07:48:02 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 29 Aug 2011 07:48:02 +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; Mon, 29 Aug 2011 07:47:59 +0000 Received: from hel.zones.apache.org (hel.zones.apache.org [140.211.11.116]) by hel.zones.apache.org (Postfix) with ESMTP id 32536D425F for ; Mon, 29 Aug 2011 07:47:38 +0000 (UTC) Date: Mon, 29 Aug 2011 07:47:38 +0000 (UTC) From: "Lionel Cons (JIRA)" To: commits@activemq.apache.org Message-ID: <902168790.2440.1314604058202.JavaMail.tomcat@hel.zones.apache.org> Subject: [jira] [Created] (APLO-84) Log more information in case of authorization failures 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 Log more information in case of authorization failures ------------------------------------------------------ Key: APLO-84 URL: https://issues.apache.org/jira/browse/APLO-84 Project: ActiveMQ Apollo Issue Type: Improvement Reporter: Lionel Cons In case of failed plain text connection, we get: 2011-08-29 09:21:26,936 connected: local:/192.168.183.22:6123, remote:/192.168.208.50:44390 2011-08-29 09:21:26,947 STOMP connection '/192.168.208.50:44390' error: Connect not authorized. Username=monitor 2011-08-29 09:21:26,951 disconnected: local:/192.168.183.22:6123, remote:/192.168.208.50:44390 But in case of failed X.509 connection, we only get: 2011-08-29 09:21:42,961 connected: local:/192.168.183.22:6133, remote:/192.168.208.50:33530 2011-08-29 09:21:43,009 STOMP connection '/192.168.208.50:33530' error: Connect not authorized. 2011-08-29 09:21:43,011 disconnected: local:/192.168.183.22:6133, remote:/192.168.208.50:33530 Would it be possible to also log the DN that failed to authenticate? More generally, in case of authorization failure, we get minimal information: 2011-08-29 09:36:42,061 connected: local:/192.168.183.22:6133, remote:/192.168.208.50:49343 2011-08-29 09:36:42,214 STOMP connection '/192.168.208.50:49343' error: Not authorized to receive from the destination. 2011-08-29 09:36:42,217 disconnected: local:/192.168.183.22:6133, remote:/192.168.208.50:49343 Would it be possible to log more and include the identity (ideally, a list of pairs of principal kind + value) and the destination (probably as a pair of kind + name)? This extra information would greatly help creating and testing authorization rules as per APLO-56... -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira