Skip to content

[GEODE-10648] Update Pulse documentation #8077

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
JinwooHwang merged 1 commit into from
Sep 13, 2026
+2 −5
Merged

[GEODE-10648] Update Pulse documentation #8077

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
5 changes: 1 addition & 4 deletions geode-docs/tools_modules/pulse/pulse-auth.html.md.erb
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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.

## <a id="pulse-auth-https"></a>Configuring Pulse to use HTTPS

Expand Down
2 changes: 1 addition & 1 deletion geode-docs/tools_modules/pulse/pulse-hosted.html.md.erb
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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.

Expand Down
Loading