Increase user granularity and allow creating more than the 3 built in user accounts.
Increase user granularity and allow creating more than the 3 built in user accounts. For example, we have an offshore development team that would like access to their SQL instance, but can’t have access to any other instances. What I would like to do is to be able to create an account, assign permissions to that account against databases or instances, limiting the access they have to production systems. If we could get it to use AD integration rather than forms authentication as well as being able to set permissions granularly then that would be ideal.
Andy Lamb
shared this idea
SQL Monitor 5.0 introduces Active Directory integration with granular control over which user sees what. Please note that you will need to enable Active Directory authentication in order to make use of this functionality
-
Hi, yes - please see the comment here: https://sqlmonitor.uservoice.com/forums/91743-suggestions/suggestions/11653632-when-using-windows-authentication-i-want-the-read
Kind regards
-
Blaž Dakskobler
commented
Daniel - is there any special reason the read-only user role doesn't exist if you use Active Directory authentication?
That's exactly what I'm missing - a combination of a read-only access and granular control over access rights (e.g. for external people). Now I can get one or the other, but not both. -
Wayne Brantley
commented
This is best solved with AD integration
-
William Soranno
commented
I am just starting to use the 14 day trial and the idea of sharing passwords will be a show stopper for a purchase. Having AD integration and being able to specify either an AD group or user makes perfect sense. Andy thank you for the suggestion.
-
Rich James
commented
While useful to split apart the administrative and user accounts, there doesn't seem to be a provision to allow a single server (or group of servers) to be checked from a specific account. It would be useful to have 'subordinate read only' accounts that could only read a subset of the full array of servers, so departmental administrators could see their own system, without being able to see another department's system behaviour.
-
Blaž Dakskobler
commented
Yes please. Would like to give SQL Monitor access to some teams/people, but only for particular instances or even just databases.
-
Joe Cairns
commented
Absolutely support this one. Our organization will not allow some of the technical teams access to SQL Monitor until a feature like this available and this is from a PCI compliance perspective. Without being able to show what rights and individual user has and to be able to log their activity in the tool, we cant be compliant.
-
Anonymous
commented
As it stands the user roles aren't much use as we also want to assign permissions to certain databases to certain users.
-
Thanks for your feedback Andy.
-
Thanks for this suggestion, we'll add it as an enhancement for the feature.
-
Berlington Barnett
commented
Add the capacity to create custom user with general o explicit access to the system, without generic user, and a log access.
-
Thank you for your feedback Bruce. The feature has been deliberately designed with simplicity in mind, as during user-experience sessions people indicated that having to configure and manage a new set of accounts could potentially be a headache. However we will certainly take your feedback into consideration for any future work on this feature. Thanks, Fiona.
-
Bruce
commented
Multiple users is good, but if users could be restricted as to which servers they can monitor. Currently, the users are able to see all servers, which on a muti-site solution can be overwhelming.
