Public Access
jaap-jan
d3b14e6bc0
Options, JWT bearer validation, the /meta and .well-known endpoints, and a dev compose stack with Keycloak. Verified end to end: compose up, migrate, run, both discovery endpoints return correct payloads, and readiness reports the schema current. Configuration: - Strongly-typed options for Server, Oidc, Relay and Sync, all ValidateOnStart. A self-hosted server that boots half-configured and fails later per-request is far harder to diagnose than one that refuses to start and names the bad setting. - Cross-field validation the annotations cannot express: relay needs a WebSocketUrl when enabled, idle timeout must be under max session duration, item payload cap under batch cap. - Startup warnings for combinations that are individually valid but dangerous together: RequireHttpsMetadata false outside Development, and AllowEmailLinking (which turns any token bearing a victim's email into account takeover, hence default false). Auth: - JwtBearer with ClockSkew cut to 30s from the 5-minute default; five minutes of slack on a credential granting vault ciphertext access is more than any clock needs. - IncludeErrorDetails off, and a FallbackPolicy so an endpoint without an explicit policy still requires a caller rather than silently being public. Discovery, per ADR 0002: - /api/v1/meta reports versions, features and push caps. - /.well-known/dodossh-configuration is the onboarding story: the user types one server URL and the client discovers OIDC authority, client id, scopes and relay endpoint. Two environment problems found by actually running the stack: - PostgreSQL 18 changed its data mount point. Mounting /var/lib/postgresql/data — correct through 17 — makes the image refuse to start; 18+ wants a single mount at /var/lib/postgresql with the cluster in a subdirectory. - Keycloak moved to host port 18080. An unrelated Apache Tomcat on this machine holds 127.0.0.1:8080, and a loopback-specific bind beats Docker's 0.0.0.0 publish for "localhost". It presents as Keycloak 404ing every realm while its own log says the import succeeded, which is a genuinely misleading failure. Also: CA1848 is enforced, not advisory — warnings are errors, so the .editorconfig comment claiming otherwise was wrong. Startup and health logging now uses [LoggerMessage]. And a clean rebuild is back to zero warnings; the incremental build had been hiding 40 in test projects (banned Guid.NewGuid, an obsolete Testcontainers constructor, and two analyzer families that are genuinely noise under a test host). Verified: 0 warnings on a clean rebuild, 122 tests pass, format clean.
45 lines
2.0 KiB
XML
45 lines
2.0 KiB
XML
<Project>
|
|
|
|
<!-- Inherit everything from the repo root, then relax and add what test projects need. -->
|
|
<Import Project="$([MSBuild]::GetPathOfFileAbove('Directory.Build.props', '$(MSBuildThisFileDirectory)../'))" />
|
|
|
|
<PropertyGroup>
|
|
<IsPackable>false</IsPackable>
|
|
<IsTestProject>true</IsTestProject>
|
|
<!-- Test projects legitimately do things production code should not: assert on
|
|
nulls, construct throwaway objects, use reflection. Keep warnings visible
|
|
but non-fatal so a test file never blocks a build. -->
|
|
<TreatWarningsAsErrors>false</TreatWarningsAsErrors>
|
|
<!-- xunit.v3 runs on Microsoft.Testing.Platform, which needs an executable host. -->
|
|
<OutputType>Exe</OutputType>
|
|
<UseMicrosoftTestingPlatformRunner>true</UseMicrosoftTestingPlatformRunner>
|
|
<TestingPlatformDotnetTestSupport>true</TestingPlatformDotnetTestSupport>
|
|
</PropertyGroup>
|
|
|
|
<PropertyGroup Label="Analyzer relaxations for tests">
|
|
<!-- CA1707: test method names use underscores by convention (Method_State_Expectation).
|
|
CA2007: no SynchronizationContext in tests, ConfigureAwait is noise.
|
|
CA1861: inline constant arrays in theories are clearer than static fields. -->
|
|
<!--
|
|
MA0004 is the Meziantou equivalent of CA2007: there is no SynchronizationContext under
|
|
the test host, so ConfigureAwait is noise.
|
|
xUnit1051 wants TestContext.Current.CancellationToken threaded through every awaited
|
|
call. Worth doing for long-running suites; here the container fixture owns lifetime and
|
|
the assertions are short, so it buys nothing but churn.
|
|
-->
|
|
<NoWarn>$(NoWarn);CA1707;CA2007;CA1861;CA1052;CA1515;MA0004;xUnit1051</NoWarn>
|
|
</PropertyGroup>
|
|
|
|
<ItemGroup Label="Test framework — every test project gets these">
|
|
<PackageReference Include="xunit.v3" />
|
|
<PackageReference Include="Shouldly" />
|
|
<PackageReference Include="NSubstitute" />
|
|
</ItemGroup>
|
|
|
|
<ItemGroup>
|
|
<Using Include="Xunit" />
|
|
<Using Include="Shouldly" />
|
|
</ItemGroup>
|
|
|
|
</Project>
|