Forum Discussion
Connecting to SAP HANA
Just wanted to add that I'm having the same issue. I'm getting my infrastructure security folks to check that the date gateway machine can access our SAP HANA in the cloud. If we manage to fix the issue I'll post back here.
When you are creating your SAP HANA connection are you specifying a port as well? This error was happening to me because the connection creation interface wasn't very specific about the need to include a port. Once I did, the issue appeared to resolve. So, when prompted for the "server" express it like this: <servername>.<domain>.<com/net>:<port>
I'm not sure if it's a standardized thing or not, but if you just know the server name and instance number (say your instance number is "02") then your port may look something like 30215 or "3<instanceNumber>15". Otherwise maybe just try the default port of 30015.
Hope that helps.
Hello All
That last one deffinitely helped for me: 30215 or "3<instanceNumber>15" into the port number.
Thanks a lot Jeremy, Jan
Adding the port number helped. In my case it was the default 30015
Hi Jeremy,
By adding port number to the system, the error is gone. Thanks for the suggestion.
I have a question:
If I create enterprise gateway with the help of Service Account (which has global rights to all data) on SAP HANA, where's the data security when a dashboard is shared between multiple users (business end users).
Do I have to make RLS on the dashboard when developed or when a end user refreshes or view the published dashboard will they get data that is restricted in SAP.
I'm not a super expert, however it's my current understanding that the only back end that can do a kind of pseudo-sso is SSAS via the EffectiveUserName to implement the security for the consuming user on a tabular model. It doesn't actually authenticate to the model using that user's credential like a true Kerberos SSO connection, rather still authenticates as the service account used in the gateway connection but then applies security to the given user based on their EffectiveUserName...
https://powerbi.microsoft.com/en-us/documentation/powerbi-gateway-onprem-indepth/#mapping-usernames-for-analysis-services-data-sources explains more about how EffectiveUserName is used with SSAS.
To my knowledge currently, this wouldn't apply to a HANA data source. I'd make sure RLS is in place as you need for your purposes.
You need to build RLS in the dataset. User's credentials is not passed to SAP, so SAP security does not apply.
Service account is used to refresh the data.
Users who are added to the datasource have the ability to publish datasets. When the user builds the reports using Power BI Desktop, they will be using their personal login. This makes sure that SAP security is applied. E.g. While building the reports using Power BI Deskop, I have access to only those BEx queries that my user id has. Service account may have wider access.
RLS needs to added to the dataset for Business User's
