Hi Jo,
yes it is correct, the broker admin password can be masked using the
same way.
An alternative to mask password could be to use the kubernetes secrets, see
https://artemiscloud.io/documentation/operator/reference.html
Regards,
Domenco
On Fri, 6 May 2022 at 17:26, Jo De Troy wrote:
> Dome
Domenico,
thanks again.
I guess the masking can also be done for the password the admin user of the
broker, correct?
Regards,
Jo
Op vr 6 mei 2022 om 16:57 schreef Domenico Francesco Bruscino <
bruscin...@gmail.com>:
> Hi Jo,
>
> this is more a question for the ArtemisCloud.io community [1], I t
Hi Jo,
this is more a question for the ArtemisCloud.io community [1], I think the
passwords for the users in ActiveMQArtemisSecurity can be masked using the
mask command [2] but I have never tried, i.e.
$ ./broker/bin/artemis mask --hash user
result:
1024:C1475A2DBBCCC50D7EB75448555E408E99A71DA45
Thanks Domenico
Is there a possibility to encrypt/obfuscate the passwords for the users in
kind: ActiveMQArtemisSecurity ?
Or can these be stored in an Openshift secret/Hashicorp Vault/...
Best Regards,
Jo
Op vr 6 mei 2022 om 11:30 schreef Domenico Francesco Bruscino <
bruscin...@gmail.com>:
>
Hi Jo,
Apache ActiveMQ Artemis contains a flexible role-based security model for
applying security to queues, based on their addresses, see the
documentation [1] for further details.
Suppose you have userA with the roleA that can only consume queueA and
userB with roleB that can only consume queu
Hello,
I'm pretty new to the ActiveMQ (Artemis) world.
I was wondering if it's possible to define different users per queue when
using e.g. PropertiesLoginModule.
So userA would be able to only produce on queueA but not on queueB
Suppose you have a broker with a few 50 different queues you don't w
