From 3ee1f456740e92aa676575b7a20ab51022e00fd2 Mon Sep 17 00:00:00 2001 From: JinwooHwang Date: Sat, 12 Sep 2026 20:40:00 -0400 Subject: [PATCH] [GEODE-10648] Update Pulse documentation --- geode-docs/tools_modules/pulse/pulse-auth.html.md.erb | 5 +---- geode-docs/tools_modules/pulse/pulse-hosted.html.md.erb | 2 +- 2 files changed, 2 insertions(+), 5 deletions(-) diff --git a/geode-docs/tools_modules/pulse/pulse-auth.html.md.erb b/geode-docs/tools_modules/pulse/pulse-auth.html.md.erb index a7149dcb784a..3884f9aaec94 100644 --- a/geode-docs/tools_modules/pulse/pulse-auth.html.md.erb +++ b/geode-docs/tools_modules/pulse/pulse-auth.html.md.erb @@ -23,10 +23,7 @@ Pulse requires all users to authenticate themselves before they can use the Puls If you run Pulse in embedded mode, the Pulse application runs on the JMX Manager node and no JMX authentication is required. You do not need to specify valid JMX credentials to start an embedded Pulse application. -If you host Pulse on a web application server (non-embedded mode) and you configure JMX authentication on the <%=vars.product_name%> manager node, then the Pulse Web application must authenticate itself with the manager node when it starts. Specify the credentials of a valid JMX user account in the `pulse.properties` file, as described in [Hosting Pulse on a Web Application Server](pulse-hosted.html). - -**Note:** -The credentials that you specify must have both read and write privileges in the JMX Manager node. See [Configuring a JMX Manager](../../managing/management/jmx_manager_operations.html#topic_263072624B8D4CDBAD18B82E07AA44B6). +If you host Pulse on a web application server (non-embedded mode) and you configure JMX authentication on the <%=vars.product_name%> manager node, Pulse does not use a separate account of its own. Activate the <%=vars.product_name%> security profile, described below, and each user signs in with their own credentials, which Pulse uses to connect to the JMX Manager. ## Configuring Pulse to use HTTPS diff --git a/geode-docs/tools_modules/pulse/pulse-hosted.html.md.erb b/geode-docs/tools_modules/pulse/pulse-hosted.html.md.erb index 36468eefdaa3..d7b3b9399139 100644 --- a/geode-docs/tools_modules/pulse/pulse-hosted.html.md.erb +++ b/geode-docs/tools_modules/pulse/pulse-hosted.html.md.erb @@ -106,7 +106,7 @@ your Web application server. For example, with Tomcat the default URL is `http://*address*:8080/pulse`. Your application server provides options for configuring the address, port, and application name; substitute the correct items to access the deployed Pulse application. - Pulse connects to the locator or JMX Manager that you configured in the `pulse.properties` file, authenticating using the credentials that you configured in the file. + Pulse connects to the locator or JMX Manager that you configured in the `pulse.properties` file. 9. If you have configured authentication for the Pulse application, enter the username and password of a valid Pulse account in the login screen. Otherwise, enter the default "admin" in both fields. Click **Sign In** to continue.