New On Premises Gateway (Personal Mode) with Okta

[galbraithag]

We saw the notice that the old Desktop Gateway is being decommissioned on July 31,2017, so we downloaded the new on -premises gateway (personal mode).  When logging into microsoft to register the gateway, we get HTTPS errors.  After researching the errors, we tried a few different suggestions out there:

1) changing the config file from Auto to Https

        a) This did not work and we got the same results

2) Logging in with an O365 Account, not associated with OKTA corporate solution

        a) this allowed me to log into the gateway, however this did not associate my Power BI Tenant to my local machine, because             they are not associated through OKTA (its like the two accounts were not in sync).

Does anyone have any suggestions on how to get the gateway to connect while using OKTA?  

Thanks,

Andrew 

[v-huizhn-msft]

Hi @galbraithag,

A gateway is software that facilitates access to data that is stored on a private, on-premises network, then enables you to use that data in online services like the Power BI service.  It acts as a bridge, providing quick and secure data transfer between the Power BI service and on-premises data sources.

>>1) changing the config file from Auto to Https

After that, please use your Power BI account to sign in and check it it wokrs fine.

2) You have two accounts, O365 account and another Power BI account? Please use the Powr BI account to sign in gateway, so it works as a bridge. I am not specific about OKTA, please share more details for further analysis.

Best Regards,
Angelia

[kpazandak]

Can you point me to the name of the config file where this settings is switched?