describe API calls made by the cf client (#7351)

hashicorp · Aug 22, 2019 · 2f74e97 · 2f74e97
1 parent db0f2f3
commit 2f74e97
Showing 1 changed file with 8 additions and 0 deletions.
diff --git a/website/source/docs/auth/pcf.html.md b/website/source/docs/auth/pcf.html.md
@@ -188,6 +188,14 @@ $ cf org-users my-example-org
 $ cf set-org-role vault my-example-org OrgManager
 ```
 
+Specifically, the `vault` user created here will need to be able to perform the following API calls:
+
+- Method: "GET", endpoint: "/v2/info"
+- Method: "POST", endpoint: "/oauth/token"
+- Method: "GET", endpoint: "/v2/apps/$APP_ID"
+- Method: "GET", endpoint: "/v2/organizations/$ORG_ID"
+- Method: "GET", endpoint: "/v2/spaces/$SPACE_ID"
+
 Next, PCF often uses a self-signed certificate for TLS, which can be rejected at first 
 with an error like: