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.
frankpl From my understanding the simple answer is "yes" things work when the gateway is in the same domain. See here for reference. However, as mentioned in the link from that article to troubleshooting it appears you could have a non-domain joined machine as outlined here but there are certain trust relationships that have to be set up between the two domains.
I think it is fair to say that just randomly spinning up a seperate non-domain joined machine won't work, it requires a lot more in terms of creating some sort of linkage if the servers are not by default in the same domain.
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.