This is an automated email from the ASF dual-hosted git repository.

jbertram pushed a commit to branch main
in repository https://gitbox.apache.org/repos/asf/artemis.git


The following commit(s) were added to refs/heads/main by this push:
     new 72feeddf5b NO-JIRA fix doc syntax issue
72feeddf5b is described below

commit 72feeddf5bfe3eb939d88e1318d6b0df92e41963
Author: Justin Bertram <[email protected]>
AuthorDate: Mon Apr 6 13:03:28 2026 -0500

    NO-JIRA fix doc syntax issue
---
 docs/user-manual/_properties-login-module-warning.adoc |  9 +++++++++
 docs/user-manual/masking-passwords.adoc                | 10 +---------
 docs/user-manual/security.adoc                         | 11 +----------
 3 files changed, 11 insertions(+), 19 deletions(-)

diff --git a/docs/user-manual/_properties-login-module-warning.adoc 
b/docs/user-manual/_properties-login-module-warning.adoc
new file mode 100644
index 0000000000..bce7bd8c25
--- /dev/null
+++ b/docs/user-manual/_properties-login-module-warning.adoc
@@ -0,0 +1,9 @@
+[WARNING]
+====
+Management and CLI operations to manipulate user & role data are only 
available when using the `PropertiesLoginModule`.
+
+In general, using properties files and broker-centric user management for 
anything other than very basic use-cases is not recommended.
+The broker is designed to deal with messages.
+It's not in the business of managing users, although that functionality is 
provided at a limited level for convenience.
+LDAP is recommended for enterprise level production use-cases.
+====
\ No newline at end of file
diff --git a/docs/user-manual/masking-passwords.adoc 
b/docs/user-manual/masking-passwords.adoc
index c1ba1aebd6..de69d7a555 100644
--- a/docs/user-manual/masking-passwords.adoc
+++ b/docs/user-manual/masking-passwords.adoc
@@ -112,15 +112,7 @@ This will use the default codec to perform a `one-way` 
hash of the password and
 Passwords in `artemis-users.properties` are automatically detected as hashed 
or not by looking for the syntax `ENC(<hash>)`.
 The `mask-password` parameter does not need to be `true` to use hashed 
passwords here.
 
-[WARNING]
-====
-Management and CLI operations to manipulate user & role data are only 
available when using the `PropertiesLoginModule`.
-
-In general, using properties files and broker-centric user management for 
anything other than very basic use-cases is not recommended.
-The broker is designed to deal with messages.
-It's not in the business of managing users, although that functionality is 
provided at a limited level for convenience.
-LDAP is recommended for enterprise level production use-cases.
-====
+include::_properties-login-module-warning.adoc[]
 
 === cluster-password
 
diff --git a/docs/user-manual/security.adoc b/docs/user-manual/security.adoc
index d4dc40b063..f2cd498910 100644
--- a/docs/user-manual/security.adoc
+++ b/docs/user-manual/security.adoc
@@ -668,16 +668,7 @@ guests=guest
 As mentioned above, the 
xref:using-cli.adoc#command-line-interface[command-line interface] supports a 
command to `add` a user.
 Commands to `list` (one or all) users, `remove` a user, and `reset` a user's 
password and/or role(s) are also supported via the 
xref:using-cli.adoc#command-line-interface[command-line interface] as well as 
the normal management interfaces (e.g. JMX, web console, etc.).
 
-____
-*Warning*
-
-Management and CLI operations to manipulate user & role data are only 
available when using the `PropertiesLoginModule`.
-
-In general, using properties files and broker-centric user management for 
anything other than very basic use-cases is not recommended.
-The broker is designed to deal with messages.
-It's not in the business of managing users, although that functionality is 
provided at a limited level for convenience.
-LDAP is recommended for enterprise level production use-cases.
-____
+include::_properties-login-module-warning.adoc[]
 
 ==== LDAPLoginModule
 


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to