So I can access the advisor and I get all our relevant data (for the VMware Cloud Services one)
I invited two additional users to our Identity & Access Management tab and active users. They can both login to VCS, however when they try goto skyline application they get the denied as they have nothing associated. All three of us have the same service roles (user & admin), but they are org members, I am the org owner.
How do I associate them with the skyline account?
Fixed with VMware help - posting in case others have a similar issue.
So the problem ended up being simple. It seems the users were selecting the "my.vmware" login not the "cloud services" one. See the image below.
---------------------------------------------------------------------------------------------------------
Was it helpful? Let us know by completing this short survey here.
Hi jbgorrie,
Please confirm if the users are able to see “Skyline Advisor” and “Skyline Collector” under the Services tab on Cloud Services.
If not then the users can request access and you can approve.
How did you add the users, did you do this under identity and select skyline user access?
Hi A13xxx ,
Below steps help to add users:
Procedure
You can add more than one user at a time.
For more details refer to :
So the two users were added by the "Identity & Access Management" tab. I added them with user role for the collector, and admin role for the advisor. They also have the support role for the orginization.
When they login to the cloud portal they both see the two advisor and collector services.
Clicking on the advisor they get "! There is no account associated with your selected Org."
I do not see anything I can change on my side to associate them
Hi jbgorrie,
If there are multiple organization, please select the right organization when logging and see if we are able to login. Also, validate if the users are showing acitve under "Identity & Access Management"
Fixed with VMware help - posting in case others have a similar issue.
So the problem ended up being simple. It seems the users were selecting the "my.vmware" login not the "cloud services" one. See the image below.
---------------------------------------------------------------------------------------------------------
Was it helpful? Let us know by completing this short survey here.