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

Robert Gemmell commented on QPID-1469:
--------------------------------------

Using a broker configured with PLAIN authenticated management security (using 
the patches i provided) gives mixed results. It is not able to create or delete 
user accounts, or view the user accounts. It is however still able to set user 
rights successfully, so it would appear that the 
AMQUserManagementMBean.getCurrentJMXUser() method does still work, although 
something else isnt when using PLAIN.

Using no security/authentication, upon attempting to set rights the broker 
leave only the .tmp and .old jmxremote.access files and thus will fail to lad 
on restart, as you reported. I do not see an NPEoutput though, is it being 
caught elsewhere?

I see from your log that you were using the RMIConnector when creating the log, 
ie without management security enabled. No username/password is transmitted to 
the broker when 'logging in' with the security disabled (the MC merely mandates 
you type something, it doesnt do anything with it though unless you use 
security), so it is perhaps not surprising it should return a null value for 
the current jmx user in such a case?

> 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
>         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.

Reply via email to