Connecting to SQL Azure Database fails due to missing SSL encryption

Question

I am learning ASP.NET 5 (vNext) on my Mac. For the last day, I've been stuck trying to connect to my SQL Azure database. In that attempt, I've been using the following code:

var serverName = "[protected]";
var dbName = "[protected]";
var userId = "[protected]";
var password = "[protected]";
var sql = "SELECT * FROM Customer";

using (var database = new SqlConnection("Server=tcp." + serverName + ".database.windows.net,1433;Database=" + dbName + ";User Id=" + userId + ";Password=" + password + ";Trusted_Connection=False;Encrypt=True;Max Pool Size=25"))
{
  database.Open();
  return await database.QueryAsync<T>(sql);                     
}

When this code gets executed, an exception is thrown. The exception details looks like this:

Type:
System.NotImplementedException

Message:
SSL encryption for data sent between client and server is not implemented.

UPDATE I learned that encryption isn't supported in the framework running on Mac OS X at this time. For that reason, I updated my connection string to looks like the following:

var connectionString = "Persist Security Info=False;Integrated Security=true;Initial Catalog=" + dbName + ";server=" + serverName + ";User Id=" + userId + ";Password=" + password;

Still, when I use the connection string above, I get the following error.

Type:
System.Data.SqlClient.SqlException

Message:
Server does not exist or connection refused.

I have confirmed that my IP address is not blocked by Azure. I did this by logging into the Azure Portal and managing the SQL Server database from the Silverlight app. Yet, I'm still not sure why I'm getting this error.

If I am understanding this correctly, there is not a way to connect to a SQL Azure database at this time from ASP.NET 5 running on a Mac. Is that true? If it is not true, what am I doing wrong?

Answer 1

As you are aware vNext on Mac is under public preview.
We are still working on providing SQL connectivity. SSL encryption is not supported on Mac yet and Azure SQL DB requires one. The project is in the pipeline and we will let you know once we have something to share.
In the meanwhile if you have any other questions please let me know.

Best,
Meet Bhagdev
Program Manager, Microsoft

Answer 2

Switch to using mono as a build target. This should give you access to ssl in entity framework.