api-server: fix undefined access

When a broker with the default yaml is created, it doesn't have a
`spec.console` section, and that was leading to a crash of the UX.

README.md

@@ -42,16 +42,16 @@ adapt depending on your cluster address)
 ### Installing the operator
 
 The plugin requires having access to the operator to function. You can either
-get the operator from the hub or from the upstream repo.
+get the operator from the operatorHub or from the upstream repo.
 
-#### From the operator hub
+#### From the operatorHub
 
-Navigate to the operator hub on the console and search for: `Red Hat Integration
+Navigate to the operatorHub on the console and search for: `Red Hat Integration
 - AMQ Broker for RHEL 8 (Multiarch)` After installation the wait for the
 operator container to be up and running.
 
 > [!WARNING]
-> If you're running into an issue where the operator hub is not accessible, try
+> If you're running into an issue where the operatorHub is not accessible, try
 > to force its redeployment: `oc delete pods --all -n openshift-marketplace`
 > see https://github.com/crc-org/crc/issues/4109 for reference.
 

src/utils/api-server.tsx

@@ -262,7 +262,7 @@ const getJolokiaLoginParameters = (
   if (brokerRoutes?.length === 0 && process.env.NODE_ENV !== 'production') {
     return requestBody;
   }
-  if (!broker.spec) {
+  if (!broker.spec || !broker.spec['console']) {
     return requestBody;
   }