qpid-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Martin Ritchie (JIRA)" <qpid-...@incubator.apache.org>
Subject [jira] Commented: (QPID-1469) AMQUserManagementMBean.getCurrentJMXUser no longer returns a valid user
Date Tue, 02 Dec 2008 17:06:44 GMT

    [ https://issues.apache.org/jira/browse/QPID-1469?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12652425#action_12652425

Martin Ritchie commented on QPID-1469:

I hadn't realised that the <security> and jmxremote_optional jar were required for authentication
to take place. I thought plain text authentication was going on. 

We really do need to get authentication going over JMX, using something Apache friendly like,
mx4j from sourceforge.net would be ideal.

> AMQUserManagementMBean.getCurrentJMXUser no longer returns a valid user
> -----------------------------------------------------------------------
>                 Key: QPID-1469
>                 URL: https://issues.apache.org/jira/browse/QPID-1469
>             Project: Qpid
>          Issue Type: Bug
>          Components: Java Management : JMX Console
>    Affects Versions: M4
>            Reporter: Martin Ritchie
>            Assignee: Martin Ritchie
>         Attachments: QPID-1469-NPE-AMQUMMBean.log
> Summary:
> Currently when the password and jmxremote.access files are updated the current username
is written in to the file as an audit trail.
> This used to work fine however we are now seeing a NullPointerException when performing
any updates such as:
> Set Rights
> Delete User

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message