[
https://issues.apache.org/jira/browse/ARTEMIS-3765?focusedWorklogId=753651&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-753651
]
ASF GitHub Bot logged work on ARTEMIS-3765:
-------------------------------------------
Author: ASF GitHub Bot
Created on: 06/Apr/22 20:13
Start Date: 06/Apr/22 20:13
Worklog Time Spent: 10m
Work Description: ahoffer commented on code in PR #4019:
URL: https://github.com/apache/activemq-artemis/pull/4019#discussion_r844366597
##########
artemis-hawtio/artemis-plugin/src/main/webapp/plugin/js/components/browse.js:
##########
@@ -326,7 +326,7 @@ var Artemis;
header: 'User ID'
},
{
- itemField: 'StringProperties',
+ itemField: 'validatedUser',
header: 'Validated User',
templateFn: function(value) {
return value._AMQ_VALIDATED_USER;
Review Comment:
The line `header: 'Validated User'` was already in main. I don't know what
it does
Issue Time Tracking
-------------------
Worklog Id: (was: 753651)
Time Spent: 0.5h (was: 20m)
> Display validated user in Hawtio
> --------------------------------
>
> Key: ARTEMIS-3765
> URL: https://issues.apache.org/jira/browse/ARTEMIS-3765
> Project: ActiveMQ Artemis
> Issue Type: New Feature
> Reporter: Aaron Hoffer
> Priority: Major
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> As a troubleshooter in the field, I would like to see the validated username
> of a client in Hawtio, so that I can understand which client is producing or
> consuming certain messages.
>
> Our project use Hawtio to view the state of Artemis, and to troubleshoot
> problems in the field. We recently switched to 2-way TLS for authentication.
> A side effect of the change was that the "User" field in Hawtio became blank
> for some clients, probably because they stopped sending username to
> authenticate.
>
> I have forked the Artemis GitHub repos, and I am ready to push a PR. I will
> use this ticket number in the branch and PR names.
>
>
>
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
