Configure the System Properties List

This feature is available since Bloomreach Experience Manager 17.1.0

Overview

This page describes how to hide specific JVM system properties from the CMS Admin System Properties panel.

When to Use

Configure the system properties hidden list when you want to prevent sensitive or irrelevant JVM properties from being visible in the CMS Admin interface. Common candidates include database credentials, internal file paths, API keys, or any property whose value should not be exposed to administrators who have access to the System Properties panel.

Background

Bloomreach Experience Manager includes a System Properties panel in the CMS Admin perspective (accessible via **Admin > System Properties**). This panel displays all JVM system properties — key-value pairs set on the JVM at startup or during runtime — in a sortable table.

By default, all JVM system properties are displayed. Starting from version 17.1, it's possible to configure a list to suppress specific properties from this view.

The exclusion is display-only. Properties listed in the list are still active in the JVM and accessible via `System.getProperty()`. Only their visibility in the CMS Admin UI is affected.

Hidden List Configuration

Configure the list in the content repository at:

/hippo:configuration/hippo:frontend/cms/cms-static/systemprops/hidden.properties

Add your string values to the property. Each value is the exact, case-sensitive, key of a JVM system property to hide. Properties not present in the JVM are silently ignored.

Default Configuration

By default, an empty hidden.properties property is present, and all system properties are shown.

Example Configuration

Once custom values are added in a local enviroment, and the repository changes are auto-exported, a yaml snippet would look like this

/hippo:configuration/hippo:frontend/cms/cms-static/systemprops:
  hidden.properties: [java.class.path, sun.java.command, com.example.db.password]

The yaml can be used to package and distribute the values across deployed environments. Alternatively, you may change the values at runtime on deployed enviroments, if there is access to the console app.

Did you find this page helpful?
How could this documentation serve you better?
On this page
    Did you find this page helpful?
    How could this documentation serve you better?