Integrate Claims Based data filtering about easydata HOT 5 CLOSED

Hello@fasteddys,

Can I ask, why did you close the issue?

We are still going to implement the requested functionality in one of the upcoming releases.

from easydata.

We will investigate this.
Could you please describe the scenario you would like to implement, so we could create a sample for exactly that (or a similar) scenario and understand what enhancements must be added to the library (if there are needed at all).

from easydata.

Hi Korzh,

As you are aware, businesses want to secure their data (on what they want to display to the user, based on his background or group, not just role.), for e.g. in our store many people log in to quickly check data and inventory.

For e.g. 1 store owner and 3 store managers, 8 outside vendor managers for cleaning, (all 11 total mgrs/role. have management roles to approve job/timesheet) in different places are also logging in. But only the the 3 finance managers this is a claim, should be allowed to see finance table , loan table data, pay table.

Because its regional for this small store, roles do not work. Claims allow you to add security to that data table, its more flexible. https://docs.microsoft.com/en-us/aspnet/core/security/authentication/claims?view=aspnetcore-6.0

In my current/previous application, they have a page with a table to add new claims (nothing but text), then map those to groups or data, just like Active Directory.

Ours is only a store with vendors etc. But your solution will work with multitenants if you have claims.

Another nice explanation

from easydata.

Ohh that's great, I wasn't sure. There are samples on claims, let me share the current feature from another product the use.

Manage and apply claims:

Basically you need a MVC view to create new claims and assign them to the user.
Another MVC view to create new claims and assign to role.
You can also setup the claims for the entity/VM so that only those have those claims.

Help page

setup Startup.cs

  
    services.AddAuthorization(options =>
    {
         // then what every you collected from korzh view to manage claims collect then
        options.AddPolicy("Claim_Name", x => x.RequireClaim("Claim_Name"));
    });

Then inside the UI

    if ((AuthorizationService.AuthorizeAsync(User, "Claim_Name")).Result.Succeeded){
        //show Korzh ui Grid element
    }

When you need to get your claim user this helper

public static string GetKorzhSpecificClaim(this ClaimsIdentity claimsIdentity, string claimType)
{
    var claim = claimsIdentity.Claims.FirstOrDefault(x => x.Type == claimType);

    return (claim != null) ? claim.Value : string.Empty;
}

To claim on user

@((ClaimsIdentity) User.Identity).GetSpecificClaim("someclaimtype")

from easydata.

Hello@fasteddys,

Can I ask, why did you close the issue?

We are still going to implement the requested functionality in one of the upcoming releases.

Hi Korzh,

First, thank you for this amazing app. I was wondering if the claim-based solution is released yet. I was looking for options to implement token-based authentication in the react sample project.

Thank you,
Zubi

from easydata.