Forum Discussion
Gateway Access to Non-Domain Joined Computer Running Analysis Services
I can confirm that after setting up domain and joining the computer running the gateway and SSAS to it, adding a domain account and giving it permission to the AS database, and adapting the user mapping to use that user, I got this working.
Hi Eno1978,
thank you for your answer. Actually, the gateway and the Analysis Services server are running on the same machine, hence connectivity between the gateway and Analysis Services should not be an issue. But apparently, there is an assumption in the gateway impersonation code that the effective user name is a domain account, not a local account. The section about authentication to AS in the first document you linked explicitly talks about the "local Active Directory".
Connecting to a relational SQL Server database on this non-domain joined computer through the same gateway is no problem, this is just an issue for Analysis Services.
Ok, so I will have to set up a domain for this computer, just to be able to connect to Analysis Services from PBI. This makes connecting to Analysis Services a bit less easy to set up.
Frank
I can confirm that after setting up domain and joining the computer running the gateway and SSAS to it, adding a domain account and giving it permission to the AS database, and adapting the user mapping to use that user, I got this working.