JJConsulting.Infinity.Client.AspNetCore 1.5.0-rc.9

JJConsulting.Infinity.Client.ReverseProxy

Configure the regular Infinity client with a token containing the ReverseProxyRegistration permission, then add automatic registration:

builder.Services
    .AddInfinityClient(options =>
    {
        options.BaseAddress = builder.Configuration["Infinity:BaseAddress"]!;
        options.Token = builder.Configuration["Infinity:Token"]!;
    })
    .AddReverseProxyAutoRegistration(options =>
    {
        options.AppName = "Orders";
        options.PathPrefix = "orders";
        options.Routes.Add(new()
        {
            Path = "/openapi/v1.json",
            AuthenticationMode = ReverseProxyAuthenticationMode.Anonymous,
            RouteType = ReverseProxyRouteType.OpenApi
        });
    });

Address and InstanceId can be explicitly configured. When omitted, the hosted service discovers the ASP.NET Core server address and creates a process-unique instance ID.

Auto-registration is disabled by default when the host environment is Development. Destinations can be configured manually in Infinity. To explicitly enable auto-registration during development:

options.IsDisabled = false;

Menu synchronization

To synchronize the application's menu at startup, chain .AddMenuItems<OrdersMenuItemProvider>() after AddReverseProxyAutoRegistration. Implement IMenuConfigurationProvider from JJConsulting.Infinity.Domain.Contracts with ValueTask ConfigureAsync(MenuConfigurationBuilder, CancellationToken). The provider is resolved in a DI scope, and its items are synchronized using the configured AppName.

using JJConsulting.Infinity.Domain.Contracts;
using JJConsulting.Infinity.Domain.Identity.Security;
using JJConsulting.Infinity.Domain.Menu;

public sealed class OrdersMenuItemProvider : IMenuConfigurationProvider
{
    public ValueTask ConfigureAsync(MenuConfigurationBuilder builder, CancellationToken cancellationToken = default)
    {
        builder.AddFolderMenuItem(new FolderMenuItem
        {
            Id = Guid.Parse("7d92e2cb-e351-4704-a305-84027c279fbb"),
            Name = "Orders",
            Order = 1,
            Authorization = new AuthorizationData()
        }, children =>
        {
            children.AddUrlMenuItem(new UrlMenuItem
            {
                Id = Guid.Parse("62d256f3-672c-4d5e-a3cd-c5660278bbef"),
                Name = "All orders",
                Slug = "orders",
                Url = "/Orders",
                Order = 1,
                Authorization = new AuthorizationData()
            });
        });
        return ValueTask.CompletedTask;
    }
}

Both AddUrlMenuItem and AddFolderMenuItem return void. Add nested folders and links inside the optional folder lambda, which receives another MenuConfigurationBuilder. The builder sets ParentId to the containing folder's ID, or null for root items, overwriting any supplied value. Assign stable IDs before adding items. See Menu service for a nested example and flat-list navigation with MenuTree.

The token also needs the Menu permission, and the application identified by AppName must already exist in Infinity. Configure the complete, nonempty menu tree: synchronization replaces the application's menu and updates its roles from each item's authorization data. Use stable, nonempty, unique IDs. Set Roles or Users in AuthorizationData to grant menu access to non-administrators. URLs are paths within the proxied application.

See Infinity.Client.Example for a working MVC example.