Skip to content

Commit

Permalink
adjust links
Browse files Browse the repository at this point in the history
  • Loading branch information
@akeller
akeller committed Dec 17, 2024
1 parent 7243133 commit 333c59e
Show file tree
Hide file tree
Showing 21 changed files with 17 additions and 130 deletions.
106 changes: 0 additions & 106 deletions optimize/self-managed/optimize-deployment/configuration/clustering.md
View file

This file was deleted.

2 changes: 1 addition & 1 deletion optimize/self-managed/optimize-deployment/configuration/history-cleanup.md
View file
Original file line number Diff line number Diff line change
Expand Up @@ -95,7 +95,7 @@ historyCleanup:

<TabItem value='ingestedevent'>

The age of ingested event data is determined by the [`time`](../../../apis-tools/optimize-api/event-ingestion.md#request-body) field provided for each event at the time of ingestion.
The age of ingested event data is determined by the [`time`](##request-body) field provided for each event at the time of ingestion.

To enable the cleanup of event data, the `historyCleanup.ingestedEventCleanup.enabled` property needs to be set to `true`.

Expand Down
2 changes: 0 additions & 2 deletions optimize/self-managed/optimize-deployment/configuration/system-configuration.md
View file
Original file line number Diff line number Diff line change
Expand Up @@ -88,8 +88,6 @@ These values control mechanisms of Optimize related security, e.g. security head
| |
| security.auth.token.lifeMin | 60 | Optimize uses token-based authentication to keep track of which users are logged in. Define the lifetime of the token in minutes. |
| security.auth.token.secret | null | Optional secret used to sign authentication tokens, it's recommended to use at least a 64-character secret. If set to `null` a random secret will be generated with each startup of Optimize. |
| security.auth.superUserIds | [ ] | List of user IDs that are granted full permission to all collections, reports, and dashboards. <br /><br /> Note: For reports, these users are still required to be granted access to the corresponding process/decision definitions in Camunda 7 Admin. See [Authorization Management](#). |
| security.auth.superGroupIds | [ ] | List of group IDs that are granted full permission to all collections, reports, and dashboards. All members of the groups specified will have superuser permissions in Optimize. <br /><br />Note: For reports, these groups are still required to be granted access to the corresponding process/decision definitions in Camunda 7 Admin. See [Authorization Management](#). |
| security.responseHeaders.HSTS.max-age | 63072000 | HTTP Strict Transport Security (HSTS) is a web security policy mechanism which helps to protect websites against protocol downgrade attacks and cookie hijacking. This field defines the time, in seconds, that the browser should remember that this site is only to be accessed using HTTPS. If you set the number to a negative value no HSTS header is sent. |
| security.responseHeaders.HSTS.includeSubDomains | true | HTTP Strict Transport Security (HSTS) is a web security policy mechanism which helps to protect websites against protocol downgrade attacks and cookie hijacking. If this optional parameter is specified, this rule applies to all the site’s subdomains as well. |
| security.responseHeaders.X-XSS-Protection | 1; mode=block | This header enables the cross-site scripting (XSS) filter in your browser. Can have one of the following options:<ul><li> `0`: Filter disabled. </li><li> `1`: Filter enabled. If a cross-site scripting attack is detected, in order to stop the attack, the browser will sanitize the page. </li><li> `1; mode=block`: Filter enabled. Rather than sanitize the page, when a XSS attack is detected, the browser will prevent rendering of the page.</li><li> `1; report=http://[YOURDOMAIN]/your_report_URI`: Filter enabled. The browser will sanitize the page and report the violation. This is a Chromium function utilizing CSP violation reports to send details to a URI of your choice.</li></ul> |
Expand Down
2 changes: 1 addition & 1 deletion ...mize/self-managed/optimize-deployment/migration-update/camunda-8/3.9-to-3.10.md
View file
Original file line number Diff line number Diff line change
Expand Up @@ -49,7 +49,7 @@ From Optimize 3.10.4, the minimum version of Java that Optimize supports is now

### Plugins

From 3.10.4, Optimize runs with Spring Boot 3. As a result, some plugin interfaces have been updated accordingly. More specifically, the [Engine Rest Filter Plugin](./../../plugins/engine-rest-filter-plugin.md) and the [Single-Sign-On Plugin](./../../plugins/single-sign-on.md) now import jakarta dependencies. If you use these plugins, you will need to adjust your implementation accordingly.
From 3.10.4, Optimize runs with Spring Boot 3. As a result, some plugin interfaces have been updated accordingly. More specifically, the [Engine Rest Filter Plugin](#) and the [Single-Sign-On Plugin](./../../plugins/single-sign-on.md) now import jakarta dependencies. If you use these plugins, you will need to adjust your implementation accordingly.

### Logging

Expand Down
1 change: 0 additions & 1 deletion optimize_sidebars.js
View file
Original file line number Diff line number Diff line change
Expand Up @@ -2915,7 +2915,6 @@ module.exports = {
"self-managed/optimize-deployment/configuration/history-cleanup",
"self-managed/optimize-deployment/configuration/localization",
"self-managed/optimize-deployment/configuration/object-variables",
"self-managed/optimize-deployment/configuration/clustering",
"self-managed/optimize-deployment/configuration/multi-tenancy",
"self-managed/optimize-deployment/configuration/common-problems",
],
Expand Down
2 changes: 1 addition & 1 deletion ...-3.11.0/self-managed/optimize-deployment/configuration/event-based-processes.md
View file
Original file line number Diff line number Diff line change
Expand Up @@ -21,7 +21,7 @@ Configuration of the Optimize event based process feature.

<span class="badge badge--platform">Camunda 7 only</span>

Configuration of the Optimize [Event Ingestion REST API](../../../apis-tools/optimize-api/event-ingestion.md) for [event-based processes](#).
Configuration of the Optimize [Event Ingestion REST API](#) for [event-based processes](#).

| YAML Path | Default Value | Description |
| ----------------------------------------------------- | ------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
Expand Down
2 changes: 1 addition & 1 deletion ...ersion-3.11.0/self-managed/optimize-deployment/configuration/history-cleanup.md
View file
Original file line number Diff line number Diff line change
Expand Up @@ -86,7 +86,7 @@ historyCleanup:

### Ingested event cleanup

The age of ingested event data is determined by the [`time`](../../../apis-tools/optimize-api/event-ingestion.md#request-body) field provided for each event at the time of ingestion.
The age of ingested event data is determined by the [`time`](##request-body) field provided for each event at the time of ingestion.

To enable the cleanup of event data, the `historyCleanup.ingestedEventCleanup.enabled` property needs to be set to `true`.

Expand Down
2 changes: 1 addition & 1 deletion .../version-3.11.0/self-managed/optimize-deployment/migration-update/2.7-to-3.0.md
View file
Original file line number Diff line number Diff line change
Expand Up @@ -44,7 +44,7 @@ The update should now successfully complete.

### Cannot disable import from particular engine

In 3.0.0, it is not possible to deactivate the import of a particular Optimize instance from a particular engine (via `engines.${engineAlias}.importEnabled`). In case your environment is using that feature for e.g. a [clustering setup](./../configuration/clustering.md), we recommend you to stay on Optimize 2.7.0 until the release of Optimize 3.1.0 (Scheduled for 14/07/2020) and then update straight to Optimize 3.1.0.
In 3.0.0, it is not possible to deactivate the import of a particular Optimize instance from a particular engine (via `engines.${engineAlias}.importEnabled`). In case your environment is using that feature for e.g. a [clustering setup](#), we recommend you to stay on Optimize 2.7.0 until the release of Optimize 3.1.0 (Scheduled for 14/07/2020) and then update straight to Optimize 3.1.0.

## Limitations

Expand Down
2 changes: 1 addition & 1 deletion ...-3.12.0/self-managed/optimize-deployment/configuration/event-based-processes.md
View file
Original file line number Diff line number Diff line change
Expand Up @@ -21,7 +21,7 @@ Configuration of the Optimize event-based process feature.

<span class="badge badge--platform">Camunda 7 only</span>

Configuration of the Optimize [event ingestion REST API](../../../apis-tools/optimize-api/event-ingestion.md) for [event-based processes](#).
Configuration of the Optimize [event ingestion REST API](#) for [event-based processes](#).

| YAML path | Default value | Description |
| ----------------------------------------------------- | ------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
Expand Down
2 changes: 1 addition & 1 deletion ...ersion-3.12.0/self-managed/optimize-deployment/configuration/history-cleanup.md
View file
Original file line number Diff line number Diff line change
Expand Up @@ -101,7 +101,7 @@ historyCleanup:

<TabItem value='ingestedevent'>

The age of ingested event data is determined by the [`time`](../../../apis-tools/optimize-api/event-ingestion.md#request-body) field provided for each event at the time of ingestion.
The age of ingested event data is determined by the [`time`](##request-body) field provided for each event at the time of ingestion.

To enable the cleanup of event data, the `historyCleanup.ingestedEventCleanup.enabled` property needs to be set to `true`.

Expand Down
2 changes: 1 addition & 1 deletion .../version-3.12.0/self-managed/optimize-deployment/migration-update/2.7-to-3.0.md
View file
Original file line number Diff line number Diff line change
Expand Up @@ -44,7 +44,7 @@ The update should now successfully complete.

### Cannot disable import from particular engine

In 3.0.0, it is not possible to deactivate the import of a particular Optimize instance from a particular engine (via `engines.${engineAlias}.importEnabled`). In case your environment is using that feature for e.g. a [clustering setup](./../configuration/clustering.md), we recommend you to stay on Optimize 2.7.0 until the release of Optimize 3.1.0 (Scheduled for 14/07/2020) and then update straight to Optimize 3.1.0.
In 3.0.0, it is not possible to deactivate the import of a particular Optimize instance from a particular engine (via `engines.${engineAlias}.importEnabled`). In case your environment is using that feature for e.g. a [clustering setup](#), we recommend you to stay on Optimize 2.7.0 until the release of Optimize 3.1.0 (Scheduled for 14/07/2020) and then update straight to Optimize 3.1.0.

## Limitations

Expand Down
2 changes: 1 addition & 1 deletion ...-3.13.0/self-managed/optimize-deployment/configuration/event-based-processes.md
View file
Original file line number Diff line number Diff line change
Expand Up @@ -21,7 +21,7 @@ Configuration of the Optimize event-based process feature.

<span class="badge badge--platform">Camunda 7 only</span>

Configuration of the Optimize [event ingestion REST API](../../../apis-tools/optimize-api/event-ingestion.md) for [event-based processes](#).
Configuration of the Optimize [event ingestion REST API](#) for [event-based processes](#).

| YAML path | Default value | Description |
| ----------------------------------------------------- | ------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
Expand Down
2 changes: 1 addition & 1 deletion ...ersion-3.13.0/self-managed/optimize-deployment/configuration/history-cleanup.md
View file
Original file line number Diff line number Diff line change
Expand Up @@ -101,7 +101,7 @@ historyCleanup:

<TabItem value='ingestedevent'>

The age of ingested event data is determined by the [`time`](../../../apis-tools/optimize-api/event-ingestion.md#request-body) field provided for each event at the time of ingestion.
The age of ingested event data is determined by the [`time`](##request-body) field provided for each event at the time of ingestion.

To enable the cleanup of event data, the `historyCleanup.ingestedEventCleanup.enabled` property needs to be set to `true`.

Expand Down
2 changes: 1 addition & 1 deletion .../version-3.13.0/self-managed/optimize-deployment/migration-update/2.7-to-3.0.md
View file
Original file line number Diff line number Diff line change
Expand Up @@ -44,7 +44,7 @@ The update should now successfully complete.

### Cannot disable import from particular engine

In 3.0.0, it is not possible to deactivate the import of a particular Optimize instance from a particular engine (via `engines.${engineAlias}.importEnabled`). In case your environment is using that feature for e.g. a [clustering setup](./../configuration/clustering.md), we recommend you to stay on Optimize 2.7.0 until the release of Optimize 3.1.0 (Scheduled for 14/07/2020) and then update straight to Optimize 3.1.0.
In 3.0.0, it is not possible to deactivate the import of a particular Optimize instance from a particular engine (via `engines.${engineAlias}.importEnabled`). In case your environment is using that feature for e.g. a [clustering setup](#), we recommend you to stay on Optimize 2.7.0 until the release of Optimize 3.1.0 (Scheduled for 14/07/2020) and then update straight to Optimize 3.1.0.

## Limitations

Expand Down
Loading

0 comments on commit 333c59e

Please sign in to comment.