like brokers can be easily configured in tests. • Basic CDI integration. • Store user’s password in hash form by default. 15.54. 1.4.0 Full release notes. 15.54.1. Highlights • "Global" limit for disk either the primary or backup is active at any given point in time, similar to how the file lock functions in the shared storage use-case. The plugin decides what 3rd party implementation is used. It could select a target sequentially from a pool, this policy is useful to evenly distribute; CONSISTENT_HASH to select a target by a key. This policy always selects the same target broker for the same key

like brokers can be easily configured in tests. • Basic CDI integration. • Store user’s password in hash form by default. 15.53. 1.4.0 Full release notes. 15.53.1. Highlights • "Global" limit for disk either the primary or backup is active at any given point in time, similar to how the file lock functions in the shared storage use-case. The plugin decides what 3rd party implementation is used. It could select a target sequentially from a pool, this policy is useful to evenly distribute; CONSISTENT_HASH to select a target by a key. This policy always selects the same target broker for the same key

like brokers can be easily configured in tests. • Basic CDI integration. • Store user’s password in hash form by default. 15.52. 1.4.0 Full release notes. 15.52.1. Highlights • "Global" limit for disk either the primary or backup is active at any given point in time, similar to how the file lock functions in the shared storage use-case. The plugin decides what 3rd party implementation is used. It could select a target sequentially from a pool, this policy is useful to evenly distribute; CONSISTENT_HASH to select a target by a key. This policy always selects the same target broker for the same key

like brokers can be easily configured in tests. • Basic CDI integration. • Store user’s password in hash form by default. 15.51. 1.4.0 Full release notes. 15.51.1. Highlights • "Global" limit for disk either the primary or backup is active at any given point in time, similar to how the file lock functions in the shared storage use-case. The plugin decides what 3rd party implementation is used. It could select a target sequentially from a pool, this policy is useful to evenly distribute; CONSISTENT_HASH to select a target by a key. This policy always selects the same target broker for the same key

like brokers can be easily configured in tests. Basic CDI integration. Store user's password in hash form by default. 1.4.0 Full release notes. Highlights: "Global" limit for disk usage. Detect Passwords in artemis-users.properties can be hashed. Such passwords should follow the syntax ENC(<hash>) . Hashed passwords can easily be added to artemis-users.properties using the user CLI command --user-command-password guest --role admin This will use the default codec to perform a "one-way" hash of the password and alter both the artemis- users.properties and artemis-roles.properties files

like brokers can be easily configured in tests. Basic CDI integration. Store user's password in hash form by default. 1.4.0 Full release notes. Highlights: "Global" limit for disk usage. Detect Passwords in artemis-users.properties can be hashed. Such passwords should follow the syntax ENC(<hash>) . Hashed passwords can easily be added to artemis-users.properties using the user CLI command --user-command-password guest --ro Security 295 This will use the default codec to perform a "one-way" hash of the password and alter both the artemis-users.properties and artemis-roles.properties files

like brokers can be easily configured in tests. Basic CDI integration. Store user's password in hash form by default. 1.4.0 Full release notes. Highlights: "Global" limit for disk usage. Detect Passwords in artemis-users.properties can be hashed. Such passwords should follow the syntax ENC(<hash>) . Hashed passwords can easily be added to artemis-users.properties using the user CLI command not work unless the broker has been started. This will use the default codec to perform a "one-way" hash of the password and alter both the artemis-users.properties and artemis-roles.properties files

like brokers can be easily configured in tests. Basic CDI integration. Store user's password in hash form by default. 1.4.0 Full release notes. Highlights: "Global" limit for disk usage. Detect Passwords in artemis-users.properties can be hashed. Such passwords should follow the syntax ENC(<hash>) . Hashed passwords can easily be added to artemis-users.properties using the user CLI command not work unless the broker has been started. This will use the default codec to perform a "one-way" hash of the password and alter both the artemis-users.properties and artemis-roles.properties files

like brokers can be easily configured in tests. Basic CDI integration. Store user's password in hash form by default. Versions 27 1.4.0 Full release notes. Highlights: "Global" limit for disk usage Passwords in artemis-users.properties can be hashed. Such passwords should follow the syntax ENC(<hash>) . Hashed passwords can easily be added to artemis-users.properties using the user CLI command --user-command-password guest --ro Security 292 This will use the default codec to perform a "one-way" hash of the password and alter both the artemis-users.properties and artemis-roles.properties files

like brokers can be easily configured in tests. Basic CDI integration. Store user's password in hash form by default. 1.4.0 Full release notes. Highlights: "Global" limit for disk usage. Detect Passwords in artemis-users.properties can be hashed. Such passwords should follow the syntax ENC(<hash>) . Hashed passwords can easily be added to artemis-users.properties using the user CLI command not work unless the broker has been started. This will use the default codec to perform a "one-way" hash of the password and alter both the artemis-users.properties and artemis-roles.properties files