You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: content/en/docs/cluster/security.md
+9-6Lines changed: 9 additions & 6 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -3,7 +3,7 @@ title: "Cluster Security"
3
3
description: "Hardening a GMT cluster installation"
4
4
lead: ""
5
5
date: 2024-10-25T01:49:15+00:00
6
-
weight: 106
6
+
weight: 108
7
7
---
8
8
9
9
@@ -13,10 +13,6 @@ In the default installation one user is installed for the database and also for
13
13
14
14
In a cluster installation we recommend restricting both.
15
15
16
-
### Deactivating the default user
17
-
18
-
TODO 🤔
19
-
20
16
### Creating a management user for delete operations
21
17
22
18
We recommend having the default user active for the API to only have *SELECT* and *INSERT* operations.
@@ -137,4 +133,11 @@ GRANT USAGE, SELECT ON SEQUENCE notes_id_seq TO client;
137
133
138
134
GRANT SELECT,INSERT ON TABLE phase_stats TO client;
139
135
GRANT USAGE, SELECT ON SEQUENCE phase_stats_id_seq TO client;
140
-
```
136
+
```
137
+
138
+
### Visibility / Deactivating the Default User
139
+
140
+
The default user has a default password and can see all runs by all other users on the system.
141
+
For additional security the default user can either be deactivated or downgraded and the password be changed.
142
+
143
+
Please note that the [User Management]({{< relref "/docs/measuring/user-management" >}}) is only part of the [Enterprise](https://www.green-coding.io/products/green-metrics-tool/) version.
0 commit comments