12

I am trying to use the "Always Encrypted" feature in SQL Server 2016 to encrypt some columns. I used this post as a guide to set the columns as encrypted in SSDT.

That part goes fine, it's when I attempt to query the data from the application that I get an error. According to the docs I need to add this:

column encryption setting=enabled

to my connection string. This does not appear to be supported in Entity Framework Core. I get this error:

column encryption setting=enabled is not supported

I tried using the SqlConnectionStringBuilder to build the string as well and the ability to add that setting is not there. It does appear to be there in .NET 4.6.

So, is anyone aware of a way to connect to an SQL server instance from a .NET Core application using Always Encrypted?

Improve this question
1

5 Answers 5

Reset to default
5

Always Encrypted is currently not supported on .Net Core

You can find the list of supported frameworks here

Adding Support for .NET core is on our roadmap, we do not have timeline for it yet

Please follow this github issue for updates

Improve this answer
Sign up to request clarification or add additional context in comments.

11 Comments

Do you have a source for this? Otherwise this answer is just opinion.
I should have mentioned this in the Answer, but, I am a part of Always Encrypted team :)
I'm also with Brian here. Have built everything using .NET Core and now really the only missing piece is getting AE to work. Would really love to use AE instead of incorporating a custom version. Any updates to this roadmap? Maybe an alpha version to test out with .NET core? ;-)
Has there been any progress on the .NET Core framework regarding Always Encrypted?
A status update would be appreciated. Or a link to the roadmap or issue in github.
|
2

Always Encrypted is now supported in the .NET Core 3.0 Preview 5 through the new Microsoft.Data.SqlClient data provider for Microsoft SQL Server.

Improve this answer

1 Comment

yup - but I can't find any samples re: how to implement Always Encrypted using this new package. Does any one have any idea how to use it?
1

As mentioned by MS folks - Always Encrypted is currently not supported on .Net Core.

  • We had the same situation, finally we had to make the Core WebApp to target .NET Full Framework, there is no other option.

  • i.e., Currently not compatible with netcoreapp1.1 (.NETCoreApp,Version=v1.1) Compatible with net452 (.NETFramework,Version=v4.5.2)

  • From forums - "Eventhough EF Core could work for AE feature, but still the underlying .NET Core SQL Client currently does not support for AE, and it will be in their (MS + Opensource ontributors) future mile stone to support it"

Please refer this GitHub page for any recent updates on this issue:

Improve this answer

1 Comment

Had same situation so we created a new project in the solution that targeted .NET46. Thought that would work but your MVC Web App also has to target .NET46.
1

It just mention here

Microsoft.data.sqlclient

Improve this answer

Comments

1

As of .net Core 3.1 this is supported. I have it running in production scenario See my Answer on this stackoverflow question (Using EFCore and Azure KeyVault) : SQL Server Always Encrypted with .NET Core not compatible

Improve this answer

Comments

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Start asking to get answers

Find the answer to your question by asking.

Ask question

Explore related questions

See similar questions with these tags.