Well I did run the update from the hub. But this isn’t the hub that is having the problem.
@webprofusion Any ideas?
@nsumner probably best to send through a support ticket with the current configuration you are trying.
The current design assumes:
- you are using 7.0.19 (hub and CCM) and that the API URL is left blank (so it defaults to the joined hub API) and Credentials are set to (None) so that it uses the instance joining credentials by default.
- the security principal for the CCM instance has been given the Managed Challenge Consumer role in the hub.
If instead you need to the API Key method to work we’d need a complete summary of all your configuration, it’s wrth deleting any existing authorization configuration add adding it again in case there are any stale parameters in the config you can’t see from the previous betas.