Can't access Workspace Portal 2.1 admin as AD user

[thakala]

Hello,

I did a fresh Workspace Portal 2.1 installation in our lab and I am having slight issues with accessing Workspace Admin portal.

Here is a screenshot of my directory BindDN settings

I have created dedicated account 'WorkspaceAdmin' for BindDN use and directory sync is working fine. However if I use 'WorkspaceAdmin' account to login to https://horizonworkspace/SAAS/admin I am directed to https://horizonworkspace/SAAS/apps/#/launcher instead.

If I access https://horizonworkpace/SAAS/login/0 and login with internal admin user I can access Workspace admin portal.

According to documentation and Workspace Connector configurator I should be able to access Workspace Admin portal with AD user I used as BindDN account, but this does not seem to be the case.

[pbjork · Accepted solution]

If you login using https://horizonworkpace/SAAS/login/0 can you see if the WorkspaceAdmin user is listed and is marked as admin user?

[thakala]

No, WorkspaceAdmin had "User" role. Once I promoted this user as Admin I am able to land on admin portal using AD account. Thank you!

Shouldn't Workspace Portal set admin role automatically on BindDN user?

[pbjork]

Yes, it should.. Did you happen not to sync it over the very first time? I can see no other reason for the automatic promoting to admin to fail..

[thakala]

Originally I had Administrator user as BindDN user, but as a afterthought I excluded administrator from Workspace Portal login. If Workspace sets admin role only for the first user used as BindDN user this explains why admin role was not set on WorkspaceAdmin user.

[pbjork]

Yes.. That makes total sense..

[HaiHuang]

Ideally, Bind DN user should be set as Administrator of Workspace. This is shown in UI of the uploaded screenshot, which saying "This user will become the Administrator for your Workspace deployment" as hint message under Bind DN text box.

We have done the tests and the results show the followings:

* When the Bind DN user is brought in as new user into Workspace, it is set as Administrator of Workspace correctly.

* However if a user account already exists in Workspace as a regular user, and it is set as Bind DN user, currently it will NOT be promoted to Administrator of Workspace. This is a bug and we should fix it.

The logged bug is: HW-38538 - Bind user is not promoted to administrator if user is already in workspace as regular user