cadenzaweb
This is basic configuration for Cadenza Web.
A simple configuration could look like:
<basicWebConfiguration>
<publicCadenzaUrl>http://localhost:8080/cadenza</publicCadenzaUrl>
<management>
<maxConcurrentUsers>10</maxConcurrentUsers>
</management>
<!-- This is just a demo secret that is not actually a
secure password, do not copy paste this
into a productive installation of Cadenza -->
<clusterSecret>d9bcdfadc8bc</clusterSecret>
</basicWebConfiguration>
This is the Content-Security-Policy configuration for Cadenza. This configuration governs how a set of HTTP headers is sent to the browser to regulate a few security settings.
The frame-ancestors configuration allows Cadenza to defend itself against
Clickjacking attacks.
Cadenza defends itself against this by setting the frame-ancestors directive
of the Content-Security-Policy header to self. This prevents Cadenza from
being embedded in sites other than itself.
If you want to allow Cadenza to be embedded into a site on another origin, then
you need to configure the origin of that site as a frame-ancestors source in
this configuration.
You can enable or disable the `Content-Security-Policy` entirely with this flag. This should *not* be disabled in production.
Default: true
Encoded cluster secret used for encrypting sensitive data on the server. In multi node environment all Cadenza nodes must use the same cluster secret. E.g. cluster secret is used to sign url to enable secure workbook report generation. Use PasswordEncoder to create encoded cluster secret.
Configuration, which maps a name to a set of labels, for use e.g. in filtering the navigator with those labels by calling the cadenza base url with the parameter labelSet and this name. E.g. http//localhost/cadenza/?labelSet={NAME}.