[jira] Commented: (QPID-1472) Management Console Delete User corrupts password file and jmxremote.access
[ https://issues.apache.org/jira/browse/QPID-1472?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12655672#action_12655672 ] Martin Ritchie commented on QPID-1472: -- I have tested the delete functionality with Linux and Windows versions of the MC. They all behave as expected. Management Console Delete User corrupts password file and jmxremote.access -- Key: QPID-1472 URL: https://issues.apache.org/jira/browse/QPID-1472 Project: Qpid Issue Type: Bug Components: Java Management : JMX Console Affects Versions: M4 Reporter: Martin Ritchie Assignee: Martin Ritchie Summary: If a user is deleted using the JMX Management Console 'Delete User' then the password file is rewritten without line endings so the content is all comments. Also due to QPID-1769 (the inability to lookup the JMX Session username) the jmxremote.access file is left as jmxremote.access.old and the new jmxremote.access.tmp is left empty, preventing the broker from starting up. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (QPID-1472) Management Console Delete User corrupts password file and jmxremote.access
[ https://issues.apache.org/jira/browse/QPID-1472?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12655064#action_12655064 ] Robert Gemmell commented on QPID-1472: -- Changes made to address QPID-1469 will prevent the jmxremote.access file corruption issue noted here, and future work to authenticate the RMIConnnector based JMX will remove the root cause. Management Console Delete User corrupts password file and jmxremote.access -- Key: QPID-1472 URL: https://issues.apache.org/jira/browse/QPID-1472 Project: Qpid Issue Type: Bug Components: Java Management : JMX Console Affects Versions: M4 Reporter: Martin Ritchie Assignee: Martin Ritchie Summary: If a user is deleted using the JMX Management Console 'Delete User' then the password file is rewritten without line endings so the content is all comments. Also due to QPID-1769 (the inability to lookup the JMX Session username) the jmxremote.access file is left as jmxremote.access.old and the new jmxremote.access.tmp is left empty, preventing the broker from starting up. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (QPID-1472) Management Console Delete User corrupts password file and jmxremote.access
[ https://issues.apache.org/jira/browse/QPID-1472?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12652157#action_12652157 ] Robert Gemmell commented on QPID-1472: -- The password file issue also (partially?) affects creating users. The password file is rewritten without line endings, but in the case I used only the first user/pass is on the first line along with the now-1-line apache license, the rest of the usernames and passwords were successfully put on their own line. Management Console Delete User corrupts password file and jmxremote.access -- Key: QPID-1472 URL: https://issues.apache.org/jira/browse/QPID-1472 Project: Qpid Issue Type: Bug Components: Java Management : JMX Console Affects Versions: M4 Reporter: Martin Ritchie Summary: If a user is deleted using the JMX Management Console 'Delete User' then the password file is rewritten without line endings so the content is all comments. Also due to QPID-1769 (the inability to lookup the JMX Session username) the jmxremote.access file is left as jmxremote.access.old and the new jmxremote.access.tmp is left empty, preventing the broker from starting up. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
