Update known issues

Author: webprofusion-chrisc

docs/hub/known-issues.md

@@ -5,12 +5,17 @@ title: Known Issues
 ## Management Hub
 
 :::info
-As we move development of *Certify Management Hub* towards a full release we will note issues that are commonly encountered here, and remove them as they are resolved.
+We will note issues that are commonly encountered here, and remove them as they are resolved.
 :::
 
-### Hub connections
-Instances of *Certify Certificate Manager* and *Certify Management Agent* services may need to be restarted (just the service, not the OS) to reconnect to a hub that has restarted or been updated. We recommend updating agents/ccm instances to the latest version corresponding to the hub when possible, although not strictly required for some minor updates.
+### Hub host operating system affects available functionality
+If you will be commonly running PowerShell etc and interacting with Windows Server using Windows Authentication you should host the Management Hub on a Windows Server install. The hub *can* be used in containers (or hosted directly on Linux) but with reduced compatibility for Windows specific things like Windows Impersonation credentials. If PowerShell and Windows networking/shares etc will matter to you, you should host your instance on Windows.
 
+### Hub and CCM/Agent Versions
+We recommend updating agents/ccm instances to the latest version corresponding to the hub when possible, although not strictly required for some minor updates.
+
+### Hub HTTPS
+If you configure https for the hub service we currently recommend a monthly scheduled restart of the service to catch certificate renewals for the service. .NET has a built in cert rotation feature (on change) but we have found that to be unreliable in current versions. In the future we will likely implement our own cert selector strategy if the issue is not resolve in .NET itself.
 
 ### User Interface
 
@@ -19,11 +24,6 @@ The UI needs to know the URL of the API it should talk to. This is configured by
 
 If the problem occurs with a new docker container, follow the above and set the url to the required host and port e.g. `http://localhost:8080`
 
-#### Data caching in the UI
-Normally, when the system changes managed certificate or updates it status the change should be streamed back to the UI via SignalR. This streaming functionality is still a work in progress and most items now update automatically.
-
-Pages that show data that might change will generally update themselves periodically (summary page, instances, charts etc) or in some cases when the underlying data changes and a message from the hub is streamed back to the UI. In some cases you may need to reload the app from the app root URL to see the latest information while the app is still under development.
-
 #### Loading time over slow connections
 The web app uses WebAssembly (WASM) and has a large application payload on initial load. Subsequent loads use cached resources.
 
@@ -35,5 +35,3 @@ Multiple instances of the Certify Agent or Management Hub service reading and wr
 
 Note: We do not provide general support for how to use different container technology and you will likely need to know more about your choice of container deployment technology than we do, if you are using containers at all. Certify Management Hub is our first product that supports deployment to containers, so we expect growing pains.
 
-### Windows Specific Tasks
-If you will be commonly running PowerShell etc and interacting with Windows Server using Windows Authentication you should host the Management Hub on a Windows Server install. The hub *can* be used in containers (or hosted directly on Linux) but with reduced compatibility for Windows specific things like Windows Impersonation credentials.