Configuration Properties
The Configuration Properties page lists every @ConfigurationProperties bean registered in the Spring Boot instance, grouped by bean class, with the property prefix and the values Spring currently binds into the bean.
Configuration Properties as
presented in Axelix UI
A scrollable list of all active @ConfigurationProperties beans, organized as expandable accordions (expanded by
default), with a search input above the list that filters beans and entries, and a counter in the form <matching> / <total>.
Configuration Properties Details
Configuration
Properties details as presented in Axelix UI
Each accordion header shows the bean class and its prefix, each row inside shows a property and the value Spring resolved for it.
- Bean Name: The class annotated with
@ConfigurationProperties. - Prefix: The property prefix bound to this bean (e.g.
spring.jpa). - Properties: One row per bean field. The displayed key is the field name (e.g.
showSql). - Value: The value Spring resolved for the field. Properties with no value are shown as
null.
By default, every value is masked as ****** for callers that do not carry the CONFIG_PROPS_VALUES_READ authority.
See Value sanitization below for how to choose which keys are masked and who sees the originals.
Value sanitization
Axelix never relies on the Spring Boot management.endpoint.configprops.show-values switch — it always asks Spring Boot
to return raw values (Show.ALWAYS) and applies its own masking on top, driven by an authority check.
Who sees raw values. Callers carrying the CONFIG_PROPS_VALUES_READ authority — granted by the built-in ADMIN
and SUPER_ADMIN roles — receive the originals. Everyone else gets values replaced with ******. See Roles and
authorities for the full
role/authority matrix.
Which keys are masked. A single starter property — axelix.sbs.endpoints.config.sanitized-properties — controls the
set, and it applies to both axelix-configprops (this page) and axelix-env (the Properties page):
- Empty list (default) — every value is masked for callers without the authority.
- Non-empty list — only the listed keys are masked; the rest are returned as-is.
axelix.sbs.endpoints.config.sanitized-properties[0]=database.password
axelix.sbs.endpoints.config.sanitized-properties[1]=spring.datasource.password
axelix.sbs.endpoints.config.sanitized-properties[2]=jwt.signing-keySee Sanitize sensitive property values in the Spring Boot Starter configuration guide for the same property described alongside the rest of the starter setup.
The standard Spring Boot Actuator properties for masking — management.endpoint.configprops.show-values,
management.endpoint.configprops.keys-to-sanitize, and their env equivalents — are not consulted. Use
axelix.sbs.endpoints.config.sanitized-properties instead.
MCP Tools
Listing every @ConfigurationProperties bean and its bound values is also exposed to AI agents through MCP. See the
MCP Tools catalog.
Enable Dedicated Actuator Endpoint
If you are on Axelix 1.2.0 or later, none of this is required: the starter registers its custom actuator endpoints by itself, and Axelix no longer requires the health/info endpoints to be enabled — it works perfectly well without them. No configuration is needed here.
The page is backed by the axelix-configprops actuator endpoint contributed by the Axelix Spring Boot Starter. Expose
it through the standard Spring Boot Actuator properties — see Configuring Spring Boot
Starter for the full list
of Axelix endpoints and surrounding setup:
management.endpoints.web.exposure.include=axelix-configpropsSee also
- Properties — runtime view of every resolved property, including the sanitization configuration shared with this page.
- Configuring Master
- Configuring Spring Boot Starter