You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@activemq.apache.org by "Justin Bertram (Jira)" <ji...@apache.org> on 2020/11/24 18:00:10 UTC

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

     [ https://issues.apache.org/jira/browse/ARTEMIS-3010?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Justin Bertram updated ARTEMIS-3010:
------------------------------------
    Summary: Document user management changes in 2.16.0  (was: Cannot manage local users offline anymore with Artemis 2.16.0)

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