18 Comments
- totally agree. It's not typical to mask a username, and for a good reason
- This is a critical feature to effectively manage the gateways and datasets.
- The gateway admin has the power to give a user access to any of the connections in the gateway but finding out exactly what (underlying data) he gives access to is actively prevented by masking the username. I can't make sense of that.
- Yes! I need to know which username was used to determine when/if the password needs to be updated.
- There are two use cases we've hit at my company in the last week. 1. Password updates against production servers -- which PBI Gateway Data Sources do I need to update, and with which password? 2. Data Access -- all data sources use credentials with read-only logins, where some logins have access to additional, more sensitive tables. The only way I know how to manage this is to know the username by data source. Please make this visible.
- Please implement this! Managing the gateway is nearly impossible without being able to see the usernames. Especially when you have multiple admins who can create connections.
- Absolutely needed. Without it I may well end up recreating the exact same data source multiple times which makes a mess. Also general comment, the UI for Managing the Gateway is a mess. Can't even sort by data source name. Have to scroll up to see properties when looking at a data source at the bottom of the list. Get some blading going here please.
- This has been a pain point since day one in managing data sources with the data gateways. Why can't those users who have admin access to gateway entries be able to see the user account registered for the credentials in that data source, especially if I am the owner of the data source!
It doesn't make sense to hide the username - it makes it harder when we have a third-party looking after our services accounts so if I need to know if somethings stuffed-up I need to give our third-party the username that they can check. Otherwise, wouldn't it be a pain if every time it happens, I have to log a ticket with MS as they can view that username from their end?
If they won't unmask it - can a work around be just to add a free text field when you create a Data Source??? That way, as a work-around we can just add it in the notes.
I really hope this gets more votes!
can't believe this has been a problem this long. It's such an unintuitive choice and seems like it would be an easy fix. At this point I'd settle for a notes field for each connection where we could house that sort of data.
