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
`user-file` is the name of a file containing user names and roles, one per line, with a comma between the user name and the role. Allowed roles are `readonly`, `storage_admin`, and `array_admin`. For example:
117
-
118
-
```
119
-
userA,readonly
120
-
userB,storage_admin
121
-
userC,array_admin
122
-
```
123
-
124
-
`keyvault` is the name of the keyvault in which the user passwords are stored. `nexusctl` generates these passwords.
125
-
126
-
If a user in the given list already exists on the appliance, their account and password isn't changed.
127
-
128
-
## Delete users on storage appliances
129
-
130
-
User accounts can be deleted on the Pure storage appliance by connecting to a control-plane or management-plane node via ssh and running the command:
`user-file` is the name of a file containing user names and roles, as described in the previous section. For each user in the list, if it exists on the appliance with the role specified, the user is deleted and their password removed from the keyvault. If the user doesn't exist on the appliance, or exists with a different role, they aren't deleted.
137
-
138
-
## List users on storage appliances
139
-
140
-
The current user accounts on the storage appliance can be listed by connecting to a control-plane or management-plane node via ssh and running the command:
141
-
142
-
```
143
-
sudo nc-toolbox nc-toolbox-breakglass nexusctl storage users get
144
-
```
145
-
146
-
## Rotate passwords for users on storage appliances
147
-
148
-
Passwords can be rotated for users on the Pure storage appliance by connecting to a control-plane or management-plane node via ssh and running the command:
`user-file` is the name of a file containing user names and roles, as described in the previous section. For each user in the list, if it exists on the appliance with the role specified, a new password is generated for the user and stored in the keyvault. If the user doesn't exist on the appliance, or exists with a different role, their password isn't changed.
0 commit comments