updated operator security section
updated the operator security section with new directions for the creation of the .pgouser file
@@ -153,32 +153,29 @@ Other settings in *pgo.yaml* are described in the [pgo.yaml Configuration](/conf
The Operator implements its own RBAC (Role Based Access Controls) for authenticating Operator users access to the Operator REST API.
-There is a default set of Roles and Users defined respectively in the following files and can be copied into your home directory as such:
+A default admin user is created when the operator is deployed. Create a .pgouser in your home directory and insert the text from below:
```
-./conf/postgres-operator/pgouser
-./conf/postgres-operator/pgorole
+pgoadmin:examplepassword
+```
+
+The format of the .pgouser client file is:
-cp ./conf/postgres-operator/pgouser $HOME/.pgouser
-cp ./conf/postgres-operator/pgorole $HOME/.pgorole
+```
+<username>:<password>
```
-Or create a *.pgouser* file in your home directory with a credential known by the Operator (see your administrator for Operator credentials to use):
+To create a unique administrator user on deployment of the operator edit this file and update the .pgouser file accordingly:
+
```
- username:password
-or
- pgouser1:password
-or
- pgouser2:password
-or
- pgouser3:password
-or
- readonlyuser:password
+$PGOROOT/deploy/install-bootstrap-creds.sh
```
-Each example above has different priviledges in the Operator. You can create this file as follows:
+After installation users can create optional Operator users as follows:
- echo "pgouser3:password" > $HOME/.pgouser
+```
+pgo create pgouser someuser --pgouser-namespaces="pgouser1,pgouser2" --pgouser-password=somepassword --pgouser-roles="somerole,someotherrole"
+```
Note, you can also store the pgouser file in alternate locations, see the
Security documentation for details.
