Upon enabling the Hub Services within Workspace ONE UEM console, I proceeded to GROUPS & SETTINGS > Configurations. Then, I searched for Intelligent Hub and clicked on LAUNCH. Afterward, I received the message stating that “This door is locked – You are not authorized to access this resource. Contact your IT administrator if you have received this message in error.”

Separately, I received the error ‘Something went wrong.’ upon completing device enrollment with VMware Intelligent Hub also after enabling Hub Services.

I was bewildered by this message since my account has the same level of access as my other environment which is Console Administrator. Upon working with VMware technical support, I was advised that Hub Services was not configured properly. To support this claim, we went to Hub Services in Workspace ONE Access (formerly known as IDM) under Catalog > Hub Configuration and clicked on Launch.

Under System Settings, there was nothing there! Not surprisingly, clicking SHOW DETAILS next to API Certificate under UEM Integration was empty as well.

Now take a look at the same section in another environment where Hub Services are configured properly.

To resolve this issue, VMware support suggested to re-configure Hub Services. Before I do, however, I pointed out that my other environment has not had Hub Services enabled in the Workspace ONE UEM console. Yet, I could see the information in the Workspace ONE Access console. How is that possible?

VMware support has yet to provide a definitive answer other than possible API corruption. With no end in sight, we decided to move forward with re-configuring Hub Services to see if it resolves the issue.

To reconfigure Hub Services in VMware Workspace ONE UEM console, go to GROUPS & SETTINGS > Configurations. Then, search for Intelligent Hub and click on the link.

Next to the Hub Services URL, click RECONFIGURE.

Before clicking CONTINUE, be sure to review the link (or click on the link topic within this prompt) to understand the possible impact.

Reconfiguring Your Workspace ONE Access Cloud Instance to use Hub Services

Fill in the Cloud Tenant URL, Username, and Password to establish communication with your Workspace ONE Access environment. Then, click TEST CONNECTION to confirm all is well and click SAVE.

Oh, dear. I’m not able to save it at all. Surprisingly, clicking CANCEL returns to the page as if Hub Services were never configured.

Also under GROUPS & SETTINGS > All Settings > System  > Enterprise Integration > VMware Identity Manager (or Workspace ONE Access), I see the CONFIGURE button which means the Service Trusts between Hub Services and UEM console is no longer configured.

I then went back to Hub Services in Workspace ONE Access (formerly known as IDM) under Catalog > Hub Configuration and clicked on Launch.

Under System Settings, once again there was nothing there! This convinces me that a critical step might have been missed before Hub Services could be enabled successfully within the VMware Workspace ONE UEM console.

Per VMware support, most likely the order of steps taken to enable the Hub Services was incorrect. Before activating Hub Services directly, we should first configure Service Trusts between Hub Services and UEM console by going to GROUPS & SETTINGS > All Settings > System  > Enterprise Integration > VMware Identity Manager (or Workspace ONE Access). Then, click on Configuration.

Click CONFIGURE to continue with the configuration.

Fill in the Tenant URL, Username, and Password. Then, click TEST CONNECTION to confirm all is well and click SAVE.

The remaining step is to activate Hub Services by going to GROUPS & SETTINGS > Configurations. Then, search for Intelligent Hub and click on the link.

As an alternative, you can also click on the 9 dot icon on the upper right-hand corner and then click Workspace ONE Hub Services.

Click on the GET STARTED button.

Hub Services should already be configured. Go ahead and review the Tenant URL and click YES to continue.

Upon activation, here’s what you will see. Go ahead and click on LAUNCH.

Viola! No more “This door is locked” error message. I also don’t get the error ‘Something went wrong.’ upon completing device enrollment with VMware Intelligent Hub. Mission accomplished.