Skip to content

Commit 0d771b3

Browse files
committed
Add instructions to disable default log masking
Revert changes
1 parent dd86a4b commit 0d771b3

File tree

4 files changed

+36
-0
lines changed

4 files changed

+36
-0
lines changed

en/identity-server/6.1.0/docs/deploy/monitor/mask-sensitive-information-in-logs.md

Lines changed: 9 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -28,3 +28,12 @@ will be masked at the Filebeat level and shipped. However, the log file itself
2828
will contain the sensitive information.
2929

3030
see, [Configure log masking with Filebeat]({{base_path}}/deploy/monitor/elk-mask-sensitive-information-in-logs)
31+
32+
## Disabling Default Log Masking
33+
34+
By default, log masking is enabled. To disable log masking, navigate to `<IS-HOME>/repository/conf/deployment.toml` and add the following configuration.
35+
36+
```toml
37+
[masking_logs]
38+
enabled = false
39+
```

en/identity-server/7.0.0/docs/deploy/monitor/mask-sensitive-information-in-logs.md

Lines changed: 9 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -16,3 +16,12 @@ Users can mask sensitive information from the logs at the time of shipping with
1616
In this feature, you can define patterns that need to be masked from the logs and it will be masked at the Filebeat level and shipped. However, the log file itself will contain sensitive information.
1717

1818
For more information, refer to [Configure log masking with Filebeat]({{base_path}}/deploy/monitor/elk-mask-sensitive-information-in-logs)
19+
20+
## Disabling Default Log Masking
21+
22+
By default, log masking is enabled. To disable log masking, navigate to `<IS-HOME>/repository/conf/deployment.toml` and add the following configuration.
23+
24+
```toml
25+
[masking_logs]
26+
enabled = false
27+
```

en/identity-server/7.1.0/docs/deploy/monitor/mask-sensitive-information-in-logs.md

Lines changed: 9 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -16,3 +16,12 @@ Users can mask sensitive information from the logs at the time of shipping with
1616
In this feature, you can define patterns that need to be masked from the logs and it will be masked at the Filebeat level and shipped. However, the log file itself will contain sensitive information.
1717

1818
For more information, refer to [Configure log masking with Filebeat]({{base_path}}/deploy/monitor/elk-mask-sensitive-information-in-logs)
19+
20+
## Disabling Default Log Masking
21+
22+
By default, log masking is enabled. To disable log masking, navigate to `<IS-HOME>/repository/conf/deployment.toml` and add the following configuration.
23+
24+
```toml
25+
[masking_logs]
26+
enabled = false
27+
```

en/identity-server/next/docs/deploy/monitor/mask-sensitive-information-in-logs.md

Lines changed: 9 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -16,3 +16,12 @@ Users can mask sensitive information from the logs at the time of shipping with
1616
In this feature, you can define patterns that need to be masked from the logs and it will be masked at the Filebeat level and shipped. However, the log file itself will contain sensitive information.
1717

1818
For more information, refer to [Configure log masking with Filebeat]({{base_path}}/deploy/monitor/elk-mask-sensitive-information-in-logs)
19+
20+
## Disabling Default Log Masking
21+
22+
By default, log masking is enabled. To disable log masking, navigate to `<IS-HOME>/repository/conf/deployment.toml` and add the following configuration.
23+
24+
```toml
25+
[masking_logs]
26+
enabled = false
27+
```

0 commit comments

Comments
 (0)