Progress on exercise 4.

data/workshop/exercise4.mdx

@@ -53,27 +53,14 @@ metadata:
 spec:
   central:
     exposure:
-      loadBalancer:
-        enabled: false
-        port: 443
-      nodePort:
-        enabled: false
       route:
         enabled: true
-    db:
-      isEnabled: Default
-      persistence:
-        persistentVolumeClaim:
-          claimName: central-db
-    persistence:
-      persistentVolumeClaim:
-        claimName: stackrox-db
   egress:
     connectivityPolicy: Offline
 EOF
 ```
 
-> Note: The values we used for the `Central` instance are all defaults, aside from `connectivityPolicy: Offline`, which tells Red Hat Advanced Cluster Security it will be operating in a disconnected environment.
+> Note: The values we used for the `Central` instance are all defaults, aside from `connectivityPolicy: Offline`, which tells Red Hat Advanced Cluster Security it will be operating in a disconnected environment. For more details on how RHACS works in a disconnected environment refer to https://docs.redhat.com/en/documentation/red_hat_advanced_cluster_security_for_kubernetes/4.5/html/configuring/enable-offline-mode.
 
 Once the `Central` resource has been created you can check the state of the RHACS pods by running `oc get pods -n acs-central` in your highside terminal. Or navigating to **Workloads** > **Pods** for the `acs-central` project in the OpenShift Web Console.
 
@@ -83,3 +70,28 @@ Once the `Central` resource has been created you can check the state of the RHAC
 | *Red Hat Advanced Cluster Security central pods*                              |
 </Zoom>
 
+Once all pods are `Running` and `Ready` you can move on to the next step.
+
+
+## 4.3 - Logging into rhacs dashboard
+
+Time to bring up our RHACS dashboard. We'll first retrieve the `admin` user password which was auto generated by the operator and stored in a `Secret`. Then we can open the `Route` for RHACS in a new browser tab and log in.
+
+1. Return to your vnc session and the open tab with our OpenShift Web Console.
+2. Click **Workloads** > **Secrets**, ensuring you are looking at the `acs-central` **Project**.
+3. Click into the `central-htpasswd` **Secret**
+4. Scroll down and click **Reveal values** on the right hand side.
+5. Copy the `password` field, we'll need this shortly.
+6. Navigate to **Networking** > **Routes** in the left hand menu.
+7. Click on the **Location** URL for the route named `central`.
+8. Login with the username `admin` and the password you copied earlier.
+
+> Note: Ironically (given the subject matter), you may receive a tls verification warning when opening the rhacs dashboard. This is expected in this short lived workshop environment (because James is lazy) and should be accepted (Kids please don't do this at home 😂).
+
+<Zoom>
+|![workshop](/static/images/compliance/central-login.gif)                       |
+|:-----------------------------------------------------------------------------:|
+| *Logging into Red Hat Advanced Cluster Security dashboard*                    |
+</Zoom>
+
+