[jira] [Comment Edited] (ARTEMIS-3010) Document user management changes in 2.16.0

["Stephan Austermühle (Jira)" <ji...@apache.org>]

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

Stephan Austermühle edited comment on ARTEMIS-3010 at 11/25/20, 3:19 PM:
-------------------------------------------------------------------------

bq. I would expect any container-based solution to allow setting the admin credentials when the broker instance is first created (e.g. as discussed here and here for Docker-based solutions)

Yes, and possible misunderstanding. Now that you have explained that twisting files directly is acceptable with Artemis, any container entrypoint can do this. (It would not have been acceptable to start the broker first with default credentials and then update through management commands or API.) 

In general, the ability to use management commands even when the broker is offline, reduces the likeliness of inconsistencies and errors so is always preferable. So, I consider direct file manipulation a step backwards. 

bq. I've clarified that in my documentation PR.

Thanks, much appreciated. Your doc update is helpful and clear.


was (Author: stephan2020):
bq. I would expect any container-based solution to allow setting the admin credentials when the broker instance is first created (e.g. as discussed here and here for Docker-based solutions)

Yes, and possible misunderstanding. Now that you have explained that twisting files directly is acceptable with Artemis, any container entrypoint can do this. (It would not have been acceptable to start the broker first with default credentials and then update through management commands or API.) 

In general, the ability to use management commands even when the broker is offline, reduces the likeliness of inconsistencies and errors so is always preferable. So I consider direct file manipulation a step backwards. 

bq. I've clarified that in my documentation PR.

Thanks, much appreciated. Your doc update is helpful and clear.

> Document user management changes in 2.16.0
> ------------------------------------------
>
>                 Key: ARTEMIS-3010
>                 URL: https://issues.apache.org/jira/browse/ARTEMIS-3010
>             Project: ActiveMQ Artemis
>          Issue Type: Task
>    Affects Versions: 2.16.0
>            Reporter: Stephan Austermühle
>            Assignee: Justin Bertram
>            Priority: Minor
>          Time Spent: 10m
>  Remaining Estimate: 0h
>
> Until Artemis 2.15 it was possible to manage local users [just as describe in the docs|https://activemq.apache.org/components/artemis/documentation/latest/security.html]:
> {code}
> ./artemis user add --user guest --password guest --role admin
> {code}
> With 2.16, it looks like the broker has to be online before users can be managed:
> {code}
> ../artemis user add --user guest --password guest --role amq
> Connection brokerURL = tcp://localhost:61616
> --user-command-user: is a mandatory property!
> Please provide the username to use for the chosen user command:
> {code}
> So, currently, it seems to be impossible to configure admin credentials before starting the broker for the first time.
> In case of the behavioral change was intended, please update the docs. Otherwise, it seems to be a bug.



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