Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Clarify how add admins and auditors #2457

Merged
merged 4 commits into from
Dec 20, 2023
Merged

Clarify how add admins and auditors #2457

Changes from 3 commits
Commits
Show all changes
4 commits
Select commit Hold shift + click to select a range
6eaffb5
Clarify how add admins and auditors}
pburkholder Dec 19, 2023
3f37b02
Update how to remove admins
pburkholder Dec 19, 2023
e80c8ab
Fix two typos
pburkholder Dec 19, 2023
d4210bd
Remove trailing backtick
pburkholder Dec 19, 2023
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
52 changes: 26 additions & 26 deletions _docs/ops/managing-users.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -56,52 +56,52 @@ Make sure you have a copy of the [cg-scripts repository](https://github.com/18F/

### Creating Admins

First, target and get a token for the main CloudFoundry UAA, and make the user a CloudFoundry admin using their GSA email address.
Make the user a Production CloudFoundry admin using their GSA email address.

```sh
cd /path/to/cg-scripts
# on a jumpbox, run this instead of the next two commands: ./uaa/login.sh
uaac target <CF_UAA_FQDN>
uaac token client get admin -s <CF_UAA_ADMINCLIENT_PASSPHRASE>
# on a production jumpbox, run:
cd ./cg-scripts
./uaa/login.sh
./make-cf-admin.sh <EMAIL_ADDRESS>
# For global auditor, instead use
# ./add-global-cf-auditor-permissions.sh <EMAIL_ADDRESS>`
pburkholder marked this conversation as resolved.
Show resolved Hide resolved
# Check permission with:
./validate-admins.sh
```

Secondly, target and get a token for the Ops UAA, and then make the user a Concourse admin using their GSA email address.

Secondly, make the user a Concourse admin in Tooling using their GSA email address.

```sh
# on a jumpbox, run this instead of the next two commands: ./uaa/login.sh
uaac target <OPS_UAA_FQDN>
uaac token client get admin -s <OPS_UAA_ADMINCLIENT_PASSPHRASE>
# on a tooling jumpbox, run:
./uaa/login.sh
./make-ops-admin.sh <EMAIL_ADDRESS>
# Verify changes with:
./validate-admins.sh
```

### Removing Admins

First, target and get a token for the main CloudFoundry UAA, and remove the user as a CloudFoundry admin using their GSA email address.
First, remove the user as a Production CloudFoundry admin using their GSA email address.

```sh
cd /path/to/cg-scripts
# on a jumpbox, run this instead of the next two commands: ./uaa/login.sh
uaac target <CF_UAA_FQDN>
uaac token client get admin -s <CF_UAA_ADMINCLIENT_PASSPHRASE>
# on a production jumpbox, run:
cd ./cg-scripts
./uaa/login.sh
./make-cf-admin.sh -r <EMAIL_ADDRESS>
# verify changes with:
./validate-admins.sh
```

Secondly, target and get a token for the Ops UAA, and then remove the user as a Concourse admin using their GSA email address.
Secondly, remove the user as a Concourse admin from Tooling using their GSA email address.

```sh
cd /path/to/cg-scripts
# on a jumpbox, run this instead of the next two commands: ./uaa/login.sh
uaac target <OPS_UAA_FQDN>
uaac token client get admin -s <OPS_UAA_ADMINCLIENT_PASSPHRASE>
# on a tooling jumpbox, run:
cd ./cg-scripts
./uaa/login.sh
./make-ops-admin.sh -r <EMAIL_ADDRESS>
```

Verify their permissions have been removed using `validate_admins.sh` and making sure their email address no longer appears in the lists.

```sh
cd /path/to/cg-scripts
./validate_admins.sh
# verify changes with:
./validate-admins.sh
```

### Deleting Admins
Expand Down
Loading