Cookie Consent<\/h2>\n
When you create an ASP.NET Core application targeting version 2.1 and run it you will see a new banner on your home page, This is the consent feature in action. This feature allows you to prompt a user to consent to your application creating \u201cnon-essential\u201d cookies. Your application should have a privacy policy and an explanation of what the user is consenting to that conforms to your GDPR requirements. By default, clicking \u201cLearn more\u201d will navigate the user to \/Privacy where you could publish the details about your app.<\/p>\n The banner itself is contained in the The GDPR gives users the right to examine the data your application holds on it, edit the data and delete the data entirely from your application. Obviously, we cannot know what data you have, where it lives or how its all linked together but what we do know is what personal data a default ASP.NET Core Identity application holds and how to delete Identity users, so we can give you a starting point. When you create an ASP.NET Core application with Individual Authentication and the data stored in-app you might notice two new options in the user profile page, Download and Delete. Download takes its data from ASP.NET Core Identity and creates a JSON file for download, delete does as you\u2019d expect, it deletes the user. You will probably have extended the identity models or added new tables to your database which uses a user\u2019s identity as a foreign key, so you will need to customize both these functions to match your own data structure and your own GDPR requirements, to do this you\u2019ll need to override the view for each of these functions. If you look at the code created in your application you will see that a lot of the old template code has vanished, this is because of the new \u201cIdentity UI as a library<\/a>\u201d feature. To override the functionality, you need to manually create the view as it would appear if ASP.NET Identity\u2019s UI were not bundled into a library. For now, until tooling arrives, this is a manual process. The Download capability is contained in Then for the corresponding .cs file you can take the default implementation from the source<\/a> as a starting point for the OnPost implementation so your version might look like the following: <\/p>\n![\"Cookie](\"https:\/\/devblogs.microsoft.com\/aspnet\/wp-content\/uploads\/sites\/16\/2018\/03\/snip_20180227142630-1-300x20.png\")
<\/a>_CookieConsentPartial.cshtml<\/code> shared view. If you open this file you can see some code showing how the user\u2019s consent value is retrieved and how it can be updated. The current consent status is exposed as an HttpFeature<\/a>, ITrackingConsentFeature<\/code>. If a user consents to allowing the use of cookies a new cookie will be created by calling CreateConsentCookie()<\/code> on the feature. The status of the user\u2019s consent can be examined by the CanTrack<\/code> property on the feature, however you don\u2019t need to do this manually, instead you can use the IsEssential<\/code> property on cookie options. For example context.Response.Cookies.Append(\"Test\", \"Value\", new CookieOptions { IsEssential = false });<\/code> would append a non-essential cookie to the response. If a user has not indicated their consent this cookie will not be appended to the response but will be silently dropped. Conversely marking a cookie as essential, context.Response.Cookies.Append(\"Test\", \"Value\", new CookieOptions { IsEssential = true });<\/code> will always create the cookie in the response, no matter the user\u2019s consent status. You can provide feedback on the cookie consent tracking feature at https:\/\/github.com\/aspnet\/Security\/issues<\/a>.<\/p>\nData Control<\/h2>\n
![\"Default](\"https:\/\/devblogs.microsoft.com\/aspnet\/wp-content\/uploads\/sites\/16\/2018\/03\/snip_20180227145719-1-300x127.png\")
<\/a>DownloadPersonalData.cshtml.cs<\/code> and the Delete capability is in DeletePersonalData.cshtml.cs<\/code>. You can see each of these files in the Identity UI GitHub repository<\/a>. For example, to override the data in the download page you must create an Account Folder under AreasIdentityPages, then a Manage folder under the account folder and finally a DownloadPersonalData.cshtml and associated DownloadPersonalData.cshtml.cs. For the cshtml file you can take the source<\/a> from GitHub as a starting point, then add your own namespace, a using statement for Microsoft.AspNetCore.Identity.UI.Pages.Account.Manage.Internal and the instruction to wire up MVC Core Tag Helpers, for example if application namespace is WebApplication21Auth the .cshtml file would look like this: <\/p>\n