[ 
https://issues.apache.org/jira/browse/ARTEMIS-3452?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17409684#comment-17409684
 ] 

Justin Bertram commented on ARTEMIS-3452:
-----------------------------------------

I just tested this on an instance of 2.18.0 and everything worked as expected. 
I created the instance with a username & password and did not allow anonymous 
access. When I opened the web console and tried to send a message it failed as 
expected since I hadn't entered the proper credentials into the "Preferences." 
Once I provided the proper credentials in the "Preferences" the send operation 
succeeded as expected.

I believe the issue with the username being {{null}} at first and then 
{{admin}} is that before you open the "Preferences" the username is not set. 
However, once you open the "Preferences" the default username is set to 
whatever you logged in with so when you try to send the message again that 
value is used hence the error message changes. In any case, as long as you set 
the proper credentials in the "Preferences" sending the message should work 
fine.

> Cannot send message from console
> --------------------------------
>
>                 Key: ARTEMIS-3452
>                 URL: https://issues.apache.org/jira/browse/ARTEMIS-3452
>             Project: ActiveMQ Artemis
>          Issue Type: Bug
>          Components: Web Console
>    Affects Versions: 2.18.0
>         Environment: Linux Server, adopt 11
>            Reporter: Bernd Köster
>            Priority: Major
>
> If I try to send a message to an adress via console, i get the message:
> Could not send message: java.lang.IllegalStateException : AMQ229031: Unable 
> to validate user from Management. Username: null; SSL certificate subject DN: 
> unavailable
> If lookup in my preferences first, the message changes to:
> Could not send message: java.lang.IllegalStateException : AMQ229031: Unable 
> to validate user from Management. Username: admin; SSL certificate subject 
> DN: unavailable
> As you can see the username is not null anymore.
> I upgrade the broker from 2.14.0 to 2.18.0. In 2.14.0 the send message worked 
> from the web console.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Reply via email to