About this package

Cookie store for use with the firewall allowing to not store any GDPR data in cookies but keep all references local. You can read and write these cookies using the User in the page request object that is injected in all your controllers.

To integrate the Cookie Store database use the UseDBCookieStore extension method as shown bellow

services.AddFireWall(FireWallTrial.License, FireWallTrial.DomainKey
, domainName: new Uri("https://www.your-domain.com", UriKind.Absolute)
, options =>
{
//your firewall settings
}).UseDBCookieStore();

You ideally would use a database to retain the cookie data that may be used by your users, the below sample shows the option where you specify a connection string

services.AddFireWall(FireWallTrial.License, FireWallTrial.DomainKey
    , domainName: new Uri("https://www.your-domain.com", UriKind.Absolute)
    , options =>
    {
        options.Cypher.ApplicationPassword = "123456$even";
        options.ApplicationName = "Name as used for reporting";
        options.ApplicationTag = "ITIL Tag";
        options.Rules.BlockRequest.BlockDuration.SlideExpiration = true;
        options.Rules.BlockRequest.BlockDuration.Expires = TimeSpan.FromSeconds(10);

        //used by JavaScript in the browser
        options.WebServices.IsUserApiUrl = new Uri(Links.IsUserEndpoint, UriKind.Relative);
        options.WebServices.RegisterLinksApiUrl = new Uri(Links.SiteMapEndPoint, UriKind.Relative);
        options.WebServices.BeaconApiUrl = new Uri(Links.BeaconPoint, UriKind.Relative);

    }).UseDBCookieStore(Configuration.GetConnectionString("FireWallCookieDatabase"));

You can see how to use it using this online documentation here: https://firewallapi.asp-waf.com/?topic=html/Overload-Walter.Web.FireWall.IUserIdentity.WriteCookie.htm

Read about reading such a cookie is documented here: https://firewallapi.asp-waf.com/?topic=html/M-Walter.Web.FireWall.IUserIdentity.TryReadCookie.htm