Enterprise Gateway On-Premises SQL Server Credentials - Use currently logged-in DOMAIN\user
For the Enterprise Gateway, when setting up an on-premises data source e.g. SQL Server, instead of explicitly specifying a Windows authenticated account, add a setting that just does "User current user" to pass on the DOMAIN\user credentials to the on-premise SQL Server.
Similarly to the SSAS implementation of using current user.
The primary use-case in mind is for usage with SQL 2016 Row Level Security, and to allow users to only see data relevant to them on their dashboards and reports, with either Imported or Direct Query.
This would be a great feature.....but I see the initial idea was logged in 2016 with no update yet.
Jon Fortner commented
I'd like to be able to setup a connection, even ODBC, where users of that connection provide their own credentials per Dataset. For example you may have a DB2 Subsystem with a thousand databases/Schemas. I'd prefer to create a generic ODBC DSN (all our users have those installed) and when the user sets a refresh, must input user credentials
Dale Syron commented
Also to allow UPN Mapping as with AS datasources
Brett Hinton commented
This would be a great idea - but hopefully wouldn't be limited to on-prem connections. SQL Azure DB connections to Power BI and Powerapps would also benefit from being able to connect as current user (which using Azure AD - should work really well)
Dave Ruijter commented
Indeed a very desirable feature!
John G Hohengarten commented
Typo: "User current user" should say "Use current User"