partial update for console 17 (#3161)

docs/enterprise/concepts.md

@@ -96,9 +96,9 @@ You may encounter a situation where you may want to add users that are not direc
 - Create a group within your identity provider directly with the non-domain users in it. This group can be found and added to Namespaces and Policies.
 - Manually add the user's unique ID. Identify the ID from a user's Session Details page, or the [Sessions](/enterprise/reference/reports.md#sessions) page in Pomerium Enterprise.
 
-   A user can see their session ID by navigating to the special `/.pomerium` URL endpoint from any Pomerium managed route. The unique ID is listed as "sub" under User Claims:
+   A user can see their session ID by navigating to the special `/.pomerium` URL endpoint from any Pomerium managed route. The unique ID is listed as "Sub" under User Details:
 
-   ![The Session Details page, showing the "sub" data](./img/session-details.png)
+   ![The User Details page, showing the "sub" data](./img/session-details.png)
 
 ## Service Accounts
 

docs/enterprise/console-settings.yaml

@@ -250,12 +250,12 @@ settings:
                 doc: |
                   Set max connection age for GRPC servers. After this interval, servers ask clients to reconnect and perform any rediscovery for new/updated endpoints from DNS.
 
-                  See https://godoc.org/google.golang.org/grpc/keepalive#ServerParameters for details
+                  See <https://godoc.org/google.golang.org/grpc/keepalive#ServerParameters> (opens new window) for details
               - name: "GRPC Server Max Connection Age Grace"
                 doc: |
                   Additive period with grpc_server_max_connection_age, after which servers will force connections to close.
 
-                  See https://godoc.org/google.golang.org/grpc/keepalive#ServerParameters (opens new window)for details
+                  See <https://godoc.org/google.golang.org/grpc/keepalive#ServerParameters> (opens new window) for details
           - name: "Tracing"
             doc: |
               Tracing tracks the progression of a single user request as it is handled by Pomerium.
@@ -288,28 +288,15 @@ settings:
 
           1. From the main menu, select **Service Accounts** under **CONFIGURE**. Click the **+ ADD SERVICE ACCOUNT** button:
 
-             ![An empty Service Accounts page](./img/add-service-account.png)
+             ![The Service Accounts page](./img/console-service-account.png)
 
           1. Service accounts can be unique and exist only for Pomerium, or impersonate directory users from your IdP.
 
-             ::::: tabs
-             :::: tab Unique
-             Give the user a unique ID. Consider referencing the Namespace you're creating it under, for easier reference later. Optionally set an expiration date:
+             Give the user a unique ID, or select an existing user to impersonate. Consider referencing the Namespace you're creating it under, for easier reference later. Optionally set an expiration date:
 
              ![Adding a unique service account](./img/create-service-account.png)
 
              The user ID set here corresponds to the `User` criteria when editing a policy.
-             ::::
-             :::: tab Impersonated
-             You can find your User ID by going to the special endpoint `/.pomerium`, or selecting **Logout** under your user in the upper right hand corner (this will not immediately log you out):
-
-             ![Session Details](./img/user-id.png)
-
-             Copy the User ID and paste it into the **User ID** field in the **Add Service Account** modal. The lookahead search should show you the user name You can also optionally set an expiration date:
-
-             ![Adding an impersonated service account](./img/create-impersonated-service-account.png)
-             ::::
-             :::::
 
           1. After you click **Submit**, the modal presents the JSON web token (**JWT**) for the service account. Temporarily save it somewhere secure, as you will not be able to view it again:
 
@@ -319,7 +306,11 @@ settings:
 
           1. Edit or create policies to give the service account access to the internal service:
 
-             ![An example policy for a service account](./img/service-account-policy.png)
+            ![An example policy for a service account](./img/create-policy-1.png)
+
+            ---
+
+            ![An example policy for a service account](./img/create-policy-2.png)
       - name: "Namespaces"
         keys: ["namespace"]
         doc: |

docs/enterprise/install/helm.md

@@ -147,9 +147,9 @@ This setup assumes an existing certificate solution using cert-manager, as descr
    sudo -E kubectl --namespace pomerium port-forward service/pomerium-proxy 443:443
    ```
 
-1. When visiting `https://console.localhost.pomerium.io`, you should see the Session List page:
+1. When visiting `https://console.localhost.pomerium.io`, you should see the Traffic:
 
-   ![The Session List page after installing Pomerium Enterprise](../img/console-session-landing.png)
+   ![The Traffic List page after installing Pomerium Enterprise](../img/console-route-traffic.png)
 
 ## Troubleshooting
 

docs/enterprise/reference/configure.md

@@ -101,14 +101,14 @@ Timeouts set the global server timeouts. Timeouts can also be set for individual
 
 Set max connection age for GRPC servers. After this interval, servers ask clients to reconnect and perform any rediscovery for new/updated endpoints from DNS.
 
-See https://godoc.org/google.golang.org/grpc/keepalive#ServerParameters for details
+See <https://godoc.org/google.golang.org/grpc/keepalive#ServerParameters> (opens new window) for details
 
 
 #### GRPC Server Max Connection Age Grace
 
 Additive period with grpc_server_max_connection_age, after which servers will force connections to close.
 
-See https://godoc.org/google.golang.org/grpc/keepalive#ServerParameters (opens new window)for details
+See <https://godoc.org/google.golang.org/grpc/keepalive#ServerParameters> (opens new window) for details
 
 
 ### Tracing
@@ -184,28 +184,15 @@ Before you begin, confirm you are in the correct Namespace. A service account ca
 
 1. From the main menu, select **Service Accounts** under **CONFIGURE**. Click the **+ ADD SERVICE ACCOUNT** button:
 
-   ![An empty Service Accounts page](./img/add-service-account.png)
+   ![The Service Accounts page](./img/console-service-account.png)
 
 1. Service accounts can be unique and exist only for Pomerium, or impersonate directory users from your IdP.
 
-   ::::: tabs
-   :::: tab Unique
-   Give the user a unique ID. Consider referencing the Namespace you're creating it under, for easier reference later. Optionally set an expiration date:
+   Give the user a unique ID, or select an existing user to impersonate. Consider referencing the Namespace you're creating it under, for easier reference later. Optionally set an expiration date:
 
    ![Adding a unique service account](./img/create-service-account.png)
 
    The user ID set here corresponds to the `User` criteria when editing a policy.
-   ::::
-   :::: tab Impersonated
-   You can find your User ID by going to the special endpoint `/.pomerium`, or selecting **Logout** under your user in the upper right hand corner (this will not immediately log you out):
-
-   ![Session Details](./img/user-id.png)
-
-   Copy the User ID and paste it into the **User ID** field in the **Add Service Account** modal. The lookahead search should show you the user name You can also optionally set an expiration date:
-
-   ![Adding an impersonated service account](./img/create-impersonated-service-account.png)
-   ::::
-   :::::
 
 1. After you click **Submit**, the modal presents the JSON web token (**JWT**) for the service account. Temporarily save it somewhere secure, as you will not be able to view it again:
 
@@ -215,7 +202,11 @@ Before you begin, confirm you are in the correct Namespace. A service account ca
 
 1. Edit or create policies to give the service account access to the internal service:
 
-   ![An example policy for a service account](./img/service-account-policy.png)
+  ![An example policy for a service account](./img/create-policy-1.png)
+
+  ---
+
+  ![An example policy for a service account](./img/create-policy-2.png)
 
 
 ## Namespaces