Fga.Net.AspNetCore 0.1.1-alpha

Auth0 FGA for .NET & ASP.NET Core

Please ensure you have a basic understanding of how FGA works before continuing: https://docs.fga.dev/

Note: This project is an early alpha and is subject to breaking changes without notice.

ASP.NET Core Setup

Before getting started, ensure you have a Store ID, Client ID, and Client Secret ready from How to get your API keys.

I'm also assuming you have authentication setup within your project, such as JWT bearer authentication via Auth0.

1. Install Fga.Net.AspNetCore from Nuget.
2. Add your StoreId, ClientId and ClientSecret to your application configuration, ideally via the dotnet secrets manager.
3. Add the following code to your ASP.NET Core configuration:

// Registers FgaAuthenticationClient & FgaAuthorizationClient, and the authorization handler
builder.Services.AddAuth0Fga(x =>
{
    x.ClientId = builder.Configuration["Auth0Fga:ClientId"];
    x.ClientSecret = builder.Configuration["Auth0Fga:ClientSecret"];
    x.StoreId = builder.Configuration["Auth0Fga:StoreId"];
});

// Register the authorization policy
builder.Services.AddAuthorization(options =>
{
    options.AddPolicy(FgaAuthorizationDefaults.PolicyKey, p => p.RequireAuthenticatedUser().AddFgaRequirement());
});

4. Create an authorization attribute that inherits from ComputedAuthorizationAttribute. From here, you can pull metadata you require to perform your tuple checks out of the HTTP request. For example, an equivalent to the How To Integrate Within A Framework example would be:

public class EntityAuthorizationAttribute : ComputedAuthorizationAttribute
{
    private readonly string _prefix;
    private readonly string _routeValue;
    public EntityAuthorizationAttribute(string prefix, string routeValue)
    {
        _prefix = prefix;
        _routeValue = routeValue;
    }

    public override ValueTask<string> GetUser(HttpContext context)
    {
        return ValueTask.FromResult(context.User.Identity!.Name!);
    }

    public override ValueTask<string> GetRelation(HttpContext context)
    {
        return ValueTask.FromResult(context.Request.Method switch
        {
            "GET" => "viewer",
            "POST" => "writer",
            _ => "owner"
        });
    }

    public override ValueTask<string> GetObject(HttpContext context)
    {
        return ValueTask.FromResult($"{_prefix}:{context.GetRouteValue(_routeValue)}");
    }
}

5. Apply the Authorize and EntityAuthorization attributes to your controller(s):

    [ApiController]
    [Route("[controller]")]
    [Authorize(FgaAuthorizationDefaults.PolicyKey)]
    public class DocumentController : ControllerBase
    {  
        [HttpGet("view/{documentId}")]
        [EntityAuthorization("doc", "documentId")]
        public string GetByConvention(string documentId)
        {
            return documentId;
        }
    }

If you need to manually perform checks, inject the IFgaAuthorizationClient as required.

An additional pre-made attribute that allows all tuple values to be hardcoded strings ships with the package (StringComputedAuthorizationAttribute). This attrbute is useful for testing and debug purposes, but should not be used in a real application.

Worker Service / Generic Host setup

Full docs coming soon.

Fga.Net ships with the AddAuth0FgaAuthenticationClient and AddAuth0FgaAuthorizationClient service collection extensions that should be self-explanatory. To use the authorization client, both clients must be registered.

Standalone client setup

Seriously consider if you need to run a standalone client before picking this option.

1. Install Fga.Net
2. Create the authorization client as below:

var client = FgaAuthorizationClient.Create(FgaAuthenticationClient.Create(), new FgaClientConfiguration()
{
    ClientId = args[0],
    ClientSecret = args[1],
    StoreId = args[2]
});

var response = await client.CheckAsync(new CheckTupleRequest()
{
    TupleKey = new TupleKey()
    {
        User = "",
        Relation = "",
        Object = ""
    }
});

Disclaimer

I am not affiliated with nor represent Auth0. All support queries regarding the underlying service should go to the Auth0 Labs Discord.