Lead your team forward
OCT 24 / 9AM ET Register nowMDM Web App Application Properties
This article is intended to serve as a reference point for MDM Web App configuration.
As such, it provides an overview of the available properties and, when applicable, refers users to more comprehensive sources.
The properties described here are defined in the mdm/etc/application.properties
file.
For each property, you will find information about the required data type, its default value, and a short description.
The Mandatory column specifies whether a property is required for the application to run and function as expected.
MDM Web App
Use these properties to specify details about the server where MDM Webbapp is running.
Name | Data Type | Default Value | Mandatory | Description |
---|---|---|---|---|
|
Number |
|
Yes |
The number of the port where the MDM Web App server is running. |
|
String |
|
Yes |
The URL of the server where the MDM Web App is running. Only used when the private and public URLs below are not defined. |
|
String |
|
No |
The private URL of the server where the MDM Web App is running. Used for communication between the the MDM Web App and the MDM backend. |
|
String |
|
No |
The public URL of the server where the MDM Web App is running. Used for communication between React-based SPAs (like the Admin Center) and the MDM backend. |
|
String |
|
Yes |
The URL of the MDM Web App server for HA read-only requests. |
|
Number |
|
Yes |
The maximum number of simultaneously opened HTTP connections between the web server and the MDM Web App server. |
MDM Features
Name | Data Type | Default Value | Mandatory | Description |
---|---|---|---|---|
|
Boolean |
|
Yes |
Enables the possibility to reset the environment from the new Admin Center (for user roles defined by the |
Keycloak
The following properties configure Keycloak. See Encrypt Passwords for information on how to encrypt passwords.
Name | Data Type | Default Value | Mandatory | Description | ||
---|---|---|---|---|---|---|
|
String |
|
Yes |
The URL of the server where Keycloak is running. |
||
|
String |
|
Yes |
The name of the Keycloak realm. |
||
|
String |
|
Yes |
The client identifier. Used to verify a user authorization token and to log in a user. |
||
|
String |
|
Yes |
Keycloak public client ID for web application browsing. |
||
|
String |
|
Yes |
Specifies the issuer of the JWT token. Typically, Keycloak uses the URL of the realm as the token issuer. |
||
|
Boolean |
|
No |
Enables access to Keycloak API with admin rights to perform health checks.
|
||
|
String |
|
Yes |
The public key of the client. |
SSL
Use these properties to set up SSL.
Name | Data Type | Default Value | Mandatory | Description |
---|---|---|---|---|
|
Boolean |
|
No |
Enables SSL. |
|
String |
/ |
No |
The full path to the keystore. |
|
String |
/ |
No |
The password for decrypting the keystore. Used if the keystore is encrypted (recommended). |
|
String |
/ |
No |
The password for the private key. Used if the private key is encrypted. |
|
String |
/ |
No |
The full path to the truststore. |
|
String |
/ |
No |
The password for the trusstore. Used if the truststore is encrypted. |
Logging
The following properties configure logging.
Name | Data Type | Default Value | Mandatory | Description |
---|---|---|---|---|
|
String |
|
No |
The root logging level.
Available values are |
|
String |
|
No |
The logging level for |
|
String |
|
No |
Logging level for MDM Web App packages. |
|
Boolean |
|
No |
If set to |
|
Boolean |
|
No |
If set to |
|
Boolean |
|
No |
If set to |
|
Boolean |
|
No |
If set to |
Endpoints for Monitoring
The following properties configure monitoring. For more information, see Monitoring Configuration.
Name | Data Type | Default Value | Mandatory | Description |
---|---|---|---|---|
|
Boolean |
|
No |
Enables all actuator endpoints.
If set to |
|
Boolean |
|
No |
Enables |
|
Boolean |
|
No |
Enables |
|
Boolean |
|
No |
Enables |
|
String |
|
No |
A comma-separated list of exposed actuator endpoints that should provide information about the application. These endpoints track the following:
|
|
String |
|
No |
Specifies how much information is provided by the
|
|
String |
|
No |
Specifies how much detail the
|
|
String |
|
No |
A comma-separated list that determines how the |
|
String |
|
No |
Configures how much information the |
|
Boolean |
|
No |
Enables |
|
String |
|
No |
Defines which components are covered by the liveness probe.
These components are a subset of |
|
String |
|
No |
Defines which components are covered by the readiness probe.
These components are a subset of |
|
String |
|
No |
Allows access to the endpoint defined in the |
|
String |
|
No |
A comma-separated list of user roles allowed to access the Prometheus endpoint. |
|
Boolean |
|
No |
Enables recording metrics for all Spring MVC requests. |
|
Boolean |
|
No |
Timing metrics to all Spring endpoints. |
|
String |
|
No |
Specifies the URL for performing health checks between MDM Web App and MDM Server. |
Client Security Headers
You can configure MDM Web App security by adding response headers (security headers) to HTTP responses from the web application.
We recommend setting security headers to help protect your web application against potential security threats. |
Name | Data Type | Default value | Mandatory | Desription |
---|---|---|---|---|
|
String |
|
No |
Specifies allowed connections. We strongly recommend using the default value. |
|
String |
|
No |
Specifies allowed script sources. We strongly recommend using the default value. |
|
String |
|
No |
Specifies allowed image sources. We strongly recommend using the default value. |
|
String |
|
No |
Protects against clickjacking.
If set to |
|
String |
|
No |
Specifies if cross-domain requests from Flash and PDF documents are allowed. |
|
String |
|
No |
Defines how much referrer information (sent with the Referer header) should be included with requests.
If set to |
|
String |
|
No |
Protects against cross-site scripting attacks.
If set to |
|
String |
|
No |
Protects against MIME sniffing. |
Retry Connection Functionality
Use the following properties to configure repeated attempts for initial connection to critical components.
MDM-gRPC Retry Setup
Name | Data Type | Default value | Mandatory | Desription |
---|---|---|---|---|
|
Number |
|
Yes |
The maximum number of attempts (including the initial call as the first attempt). |
`resilience4j.retry.configs.mdm-grpc.waitDuration |
Number |
|
Yes |
A fixed wait duration between retry attempts (in milliseconds). |
|
String |
|
Yes |
Configures a list of Throwable classes that are recorded as a failure and thus are retried. |
Was this page useful?