Skip to main content

On-premises data gateway May update is now available

We are excited to announce that we have released the May update for the On-premises data gateway. Here are some of the things that we would like to highlight with this month’s release

  • Impala SSO support using Kerberos is now available in limited preview (details below)
  • Improved support for Kerberos SSO for SAP HANA
  • The on-premises data gateway now includes the May version of the Mashup Engine

 

You can download the May release (version 14.16.6697.1) from the link below and continue reading for more details about each enhancement.

 

image

 

Impala SSO Support using Kerberos

Today we are announcing limited preview for Single Sign-On Support using Kerberos for Impala.

It is not yet globally available to everyone, but you can follow the below steps if you’d like to use it. If you have an Impala setup with single sign-on, we would love to have you try it out and send us any feedback that you have or issues you see. For more details about Kerberos SSO support in the gateway, click here.

  • Login to your Power BI account
  • Once logged in, append this query string parameter to the URL in the browser “?onPremDirectQuerySingleSignOnForExtensionImpala=true
  • In the gateway management page, add a new data source under the gateway cluster you want to use
  • Pick Impala from the “Data Source Type” list
  • Expand the “Advanced settings” section
  • Select the option to “Use SSO via Kerberos for DirectQuery queries”

 

Impala1

 

 

Improved SAP HANA Kerberos SSO Support

Kerberos single sign-on support for SAP HANA has been available for the on-premises data gateway users for some time now. Click here to learn more about it.

In this month’s release we have added a new configuration property that improves the resolution of the user principal name (UPN) on the gateway side. Over the last few months, we have heard from customers that with certain environments this resolution could fail or require special changes to their configurations. With this new property, most of those cases should be resolved. Also, with this new property, environments that have multiple AD domains (vs. a single domain) will be supported.

Below are the steps on how to configure that property. We don’t recommend doing that unless you are using SSO with SAP HANA since it’ll mildly affect the performance unnecessarily if you do.

  • In the gateway installation directory find and open this configuration file: Microsoft.PowerBI.DataMovement.Pipeline.GatewayCore.dll.config 
  • Find the “FullDomainResolutionEnabled” property and change its value to True

            <setting name=” FullDomainResolutionEnabled ” serializeAs=”String”>
                 <value>True</value>
            </setting>

 

 

Updated Version of the Mashup Engine

Last but not least, this gateway update includes the same version of the Mashup engine as the Power BI Desktop update released earlier this month. This will ensure that the reports that you publish to the Power BI Service and refresh via the gateway will go through the same query execution logic/runtime as in the latest Power BI Desktop version. Note that there are some Beta connectors that are still not supported outside of Power BI Desktop. Please refer to specific connector documentation for more details or contact us if you have any questions.

That’s all for this month’s gateway update. We hope that you find these enhancements useful and continue sending us feedback for what new capabilities you’d like to see in the future.

 

clip_image001

Additional resources:

· Try Power BI

· Follow @MSPowerBI on Twitter

· Join the conversation at the Power BI Community