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: docs.md
+11Lines changed: 11 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -104,6 +104,11 @@ places a `field.cattle.io/creatorId` annotation with the name of the user as the
104
104
105
105
If `field.cattle.io/no-creator-rbac` annotation is set, `field.cattle.io/creatorId` does not get set.
106
106
107
+
For secrets stored in the `cattle-local-user-passwords` namespace containing local users passwords:
108
+
- Verifies the password has the minimum required length.
109
+
- Verifies the password is not the same as the username.
110
+
- Encrypts the password using pbkdf2.
111
+
107
112
#### On delete
108
113
109
114
Checks if there are any RoleBindings owned by this secret which provide access to a role granting access to this secret.
@@ -518,6 +523,10 @@ When a Token is updated, the following checks take place:
518
523
519
524
### Validation Checks
520
525
526
+
#### Create
527
+
528
+
Verifies there aren't any other users with the same username.
529
+
521
530
#### Update and Delete
522
531
523
532
When a user is updated or deleted, a check occurs to ensure that the user making the request has permissions greater than or equal to the user being updated or deleted. To get the user's groups, the user's UserAttributes are checked. This is best effort, because UserAttributes are only updated when a User logs in, so it may not be perfectly up to date.
@@ -530,6 +539,8 @@ Users can update the following fields if they had not been set. But after gettin
// admitLocalUserPassword handles the secrets that contains the local user passwords, which are stored in the cattle-local-user-passwords namespace.
213
+
// If the annotation cattle.io/password-hash is not present in the secret, the webhook will encrypt it using pbkdf2. The secret is mutated to include the hashed password, the salt and the user as owner reference.
0 commit comments