The ultimate Fabric, Power BI, SQL, and AI community-led learning event. Save €200 with code FABCOMM.
Get registeredCompete to become Power BI Data Viz World Champion! First round ends August 18th. Get started.
I am trying to connect to an on-prem SQL Server DB. I use CNames (aliases) for my SQL Servers. So, I am connecting to the desired DB with a server name like cname1.domain.com. Power BI Desktop is throwing the following warning message:
Encryption Support
The server name provided doesn't match the server name on the SQL Server SSL certificate. Please contact your administrator or see the link below for more information. Alternatively, you could change your Connection encryption setting. Would you like to continue using an unencrypted connection?
If I click OK and continue with an unencrypted connection, the connection is successful. However, in doing so, am I creating a security risk? I clicked on the link that was provided, but I don't understand what it's telling me. If this is a security risk, how do I resolve it?
Solved! Go to Solution.
@Anonymous , sql server should be ssl enabled.
refer this for certificate
https://powerbi.microsoft.com/en-us/blog/ssl-security-error-with-data-source/
@Anonymous , sql server should be ssl enabled.
refer this for certificate
https://powerbi.microsoft.com/en-us/blog/ssl-security-error-with-data-source/
It turns out that, at least in my particular situation, it's more complicated than mere SSL enabling. My SQL Server data source forces encryption. So, it's not true that the connection is unencrypted when I agree to the warning message. It's the same situation as when a web server that uses an SSL certificate with a host name not specified in the certificate. The connection is still encrypted, but it's the user's choice about whether to continue browsing the site.
Because we use CNAMEs, it's just a notification that the connection string name is different than the actual SQL Server name. To resolve, I simply need to include all of the aliases and CNAMEs as subject alternative names in the certificate for the SQL Server SSL configuration.