<Project Sdk="Microsoft.NET.Sdk">

  <PropertyGroup>
    <TargetFramework>net10.0</TargetFramework>
    <ImplicitUsings>enable</ImplicitUsings>
    <Nullable>enable</Nullable>
    <TreatWarningsAsErrors>true</TreatWarningsAsErrors>
  </PropertyGroup>

  <ItemGroup>
    <!-- HttpAuditActorAccessor (Phase 3) + AddHttpContextAccessor read the
         authenticated principal off IHttpContextAccessor.HttpContext.User to
         source the audit Actor. The cookie-auth wiring in AddSecurity already
         lives here, so this is the natural home for the HTTP-backed
         principal-to-actor seam. The shared framework supplies IHttpContextAccessor
         / HttpContext (and the AddHttpContextAccessor DI helper); it also supplies
         the Extensions.* + AspNetCore.Authentication/Authorization assemblies that
         were previously listed as PackageReferences (now pruned — NU1510). -->
    <FrameworkReference Include="Microsoft.AspNetCore.App" />
    <PackageReference Include="System.IdentityModel.Tokens.Jwt" />
    <PackageReference Include="Novell.Directory.Ldap.NETStandard" />
    <PackageReference Include="ZB.MOM.WW.Auth.Abstractions" />
    <PackageReference Include="ZB.MOM.WW.Auth.Ldap" />
    <!-- Inbound-API key re-arch (C1): LibraryInboundApiKeyAdmin implements the
         Commons IInboundApiKeyAdmin management seam over the shared admin facade
         (ApiKeyAdminCommands). Security is the one project referenced by BOTH the
         Host (ManagementActor, via ManagementService) and CentralUI, and it already
         carries the rest of the Auth family — so the impl lives here. -->
    <PackageReference Include="ZB.MOM.WW.Auth.ApiKeys" />
    <PackageReference Include="ZB.MOM.WW.Auth.AspNetCore" />
    <PackageReference Include="ZB.MOM.WW.Configuration" />
  </ItemGroup>

  <ItemGroup>
    <ProjectReference Include="../ZB.MOM.WW.ScadaBridge.Commons/ZB.MOM.WW.ScadaBridge.Commons.csproj" />
  </ItemGroup>

</Project>
