Sep 02 2016 11:59 AM - edited Sep 02 2016 10:14 PM
Sep 02 2016 12:49 PM - edited Sep 02 2016 01:03 PM
Good day Karen,
You can download my presentation about : New Security Features in SQL Server 2016 - Presentation & Demo
There you can see samples for always encrypted, and some links to samples
https://gallery.technet.microsoft.com/New-Security-Features-in-8c8ca84a
In addition you can see full example step by step tutorial developing the application, here:
https://azure.microsoft.com/en-us/documentation/articles/sql-database-always-encrypted/
https://msdn.microsoft.com/en-us/library/mt757097.aspx
Feel free to ask any question :)
Sep 02 2016 01:06 PM
Thanks. Thats a great slide deck going over the DDL and the concepts, but I'm not seeing a web app or site in that.
Am I missing it?
Karen
Sep 02 2016 01:45 PM
Check the last link that I posetd above.
* I edit the message so maybe you check it before I add the last link
Anyhow, in my presentation you have links as well, I used C# simple console app for the DEMO by the way.
please informa me if still do not find the link to the app development.
Sep 02 2016 02:11 PM
Thanks. I have used the console app. I thought i'd seen a MSFT employee demo this with a website (Like Contoso), though. That's the sort of thing I'm looking for.
Sep 02 2016 02:23 PM
There is no reason for this. One of the power of using Always Encrypted is that it is almost totally transparent to the client app. You simply need to add one parameter to the connection string, and remember to use Framework 4.61 and above. The encription and decription is done in the client side (the application side), but not by your application, but by the provider (this is why we need to use the new framwork). Except of changing the connection string, there is nothing that the developer need to do in the app code.
* You do need to manage the certificate and so on, but this is not related to application and it is done the same way in any application. Therefore, if you succesfully created a console application, then you don't need to know anything more. You can create use any application that you have -> change the connection string -> and that is all, since your certificate already works with the provider (you checked in the console app).
* The only complex issue that developers might have is managing the certificate (IMO)
Sep 02 2016 02:54 PM
I'm a bit confused. There's no need to have an app/website to demo the end-to-end features of AE? How would one do that?
Or are you answering the question, which was not asked, of how to build an app differently than one that doesn't access AE data?
Sep 02 2016 10:07 PM
Hi Karen,
Soory if i am not clear :)
English is not my Native languages and it make it harder to express clearly.
I am not saying that there's no need to have an app/website to demo the end-to-end. There must be, and I gave a link to one example.
In my last rsponse, I am saying that there's no need to have an app/website to demo the end-to-end for each template of application that you have in the visual studio. The reason is that there are no differences related to code. It is not matter if you use WCF or Console app regarding the app dealing with "Always Encrypted" since the implementation is exactly the same.
@Karen Lopez wrote:Thanks. I have used the console app. I thought i'd seen a MSFT employee demo this with a website (Like Contoso), though. That's the sort of thing I'm looking for.
You said that you already used console app (after I gave you the link to the tutorial). I thought that you meant that you use console app with Always Encrypted, and you are looking for something else.
I understand that I missunderstood what you mean by "I have used the console app" :)
* we are back to my responses before....
I already gave you link to "step by step" tutorial in my first response
In addition you can see full example step by step tutorial developing the application, here:
https://azure.microsoft.com/en-us/documentation/articles/sql-database-always-encrypted/
Please check if this solve you issue :)
p.s.
* If you download the zip file to my demonstration, then you can see all the code that used (t-sql code). I did not hide anything . But in my demo I used the C# code from the above link (from Microsoft website). Therefore, instead of adding the code (which is not my) i added the same link. Check in the zip file the folder "11 AlwaysEncrypted" -> "Always_Encrypted - CS" -> "External links.txt". The file include the link to the "Step by step tutorial"
Sep 02 2016 10:12 PM
Sep 02 2016 10:20 PM
BY demo, do you mean "video"?!?
If so, then I am not familiar with one, and personaly I do not think we should create one as the textual tutorial is much simpler to follow and copy code from.
The link I posted is a full demo, but not a video.
It is a full "step by step tutorial". the tutorial starts from the SQL Server side, and it moves to the application side, just like "Contoso tutorial" (OK maybe not exactly the same as Contoso tutorial had several houndreds editing and improving and this is pretty new). Check the step with the title "Create a client application that works with the encrypted data".