You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Gateway Version: 2311 Extension Version that's been used if it applies
To Reproduce
Steps to reproduce the behavior:
Go to '..server connections then click add and connect to this server'
Click on 'settings then role based access control - click apply do not click away for at least 10 mins (seriously -until you see the green notification - do not click refresh during this time )....'
once you see that it has been applied, add a non privileged user to the local group "Windows Admin Center readers" on the server which has been created as part of the rbac process' using ad it just needs to be a domain user - the default for Mac gateway users is also domain users
4.copy the wac gateway address and logon to the gateway with the non privileged account - this works and will leave a view of the only server being the way gateway server
add the server where the rbac config has been deployed and try to authenticate - you will get "your credentials didn't work" error. and possibly some web socket errors showing up in the console from the alarm bell icon in the top rh corner
Expected behavior
it should lcomplete and add the server to the console but it didn't - the credentials were checked using the eye revealer and were correct multiple times.
I connected with admin credentials from the gateway to the rbac server and added the non privileged user to the remote management group - following that the above procedure worked and the credentials were accepted.
tried to connect to the rbac server as non privileged user (from a client machine using the Wac url) and now the error is "exception - operation blocked by rbac settings"
if I change the "manage as" credential directly on the WAC gateway itself then the non privileged user connects through to the rbac configured server as a limited access user as expected
The text was updated successfully, but these errors were encountered:
Gateway Version: 2311
Extension Version that's been used if it applies
To Reproduce
Steps to reproduce the behavior:
4.copy the wac gateway address and logon to the gateway with the non privileged account - this works and will leave a view of the only server being the way gateway server
Expected behavior
it should lcomplete and add the server to the console but it didn't - the credentials were checked using the eye revealer and were correct multiple times.
I connected with admin credentials from the gateway to the rbac server and added the non privileged user to the remote management group - following that the above procedure worked and the credentials were accepted.
tried to connect to the rbac server as non privileged user (from a client machine using the Wac url) and now the error is "exception - operation blocked by rbac settings"
if I change the "manage as" credential directly on the WAC gateway itself then the non privileged user connects through to the rbac configured server as a limited access user as expected
The text was updated successfully, but these errors were encountered: