Public Access
jaap-jan
1d262b7ccc
The whole vertical slice now runs against a real Keycloak, a real API, a real PostgreSQL and a real sshd: sign in through the browser flow, enroll with the identity-provider key binding, unlock, create a host, sync it, read it back on a second machine, unlock again with no network, accept an unseen host key, and open an interactive shell. Opt-in, because it needs the development stack; skipped with a message naming the commands. It found two bugs on its first run, and both are the same class: two sides of a stub agreeing with each other about something the specification never said. **The API never applied DodoSshJsonContext to its HTTP JSON options.** Minimal APIs therefore used the framework's web defaults, which write an enum as a number. Every request DTO carrying one failed to bind against a client writing the specified string form — which is the entire sync surface, unreachable from the real client, with a 400 naming only the parameter. The documented guarantee that request bodies reject unmapped members was likewise not in effect anywhere. Nothing caught it because the API tests posted with PostAsJsonAsync's defaults, so they and the server had independently settled on integers. Those tests now serialise through the contract, which is the deeper fix: removing the new configuration fails 13 of them. Copying settings into options a host owns is itself the hazard the context warns about, so ApplyTo lives beside the settings it mirrors and ApplyToTests pins the transformation, including that inserting the resolver leaves the caller's own in place. **The realm registered a loopback redirect URI Keycloak rejects.** `http://127.0.0.1:*/callback` looks more explicit than the RFC 8252 form and is broken: Keycloak's wildcards are trailing-only, so the `*` parses as a literal port and every authorization request came back "Invalid parameter: redirect_uri". Providers ignore the port for loopback hosts, which is the whole mechanism, so the correct registration is `http://127.0.0.1/callback` — path pinned, port free. The value the server advertises through the discovery document said the same wrong thing and now says the right one. Two smaller things, both documented in docs/platform-flags.md: - --import-realm skips a realm that already exists, so editing the realm file and restarting Keycloak changes nothing and serves stale configuration. The container has to be recreated. The compose comment claimed the opposite. - Keycloak marks its session cookies Secure even over plain HTTP, because SameSite=None requires it. A spec-conformant client drops them and the login POST answers 400 with no message; browsers complete the flow only because they exempt loopback. Harmless for the product, fatal for automation, so ScriptedBrowser carries the cookies by hand and says why. Also: the server enforces a 64 MiB floor on the passphrase KDF, so this suite cannot use the 8 MiB profile the other client suites take for speed. Those only get away with it because their in-memory servers have no policy — worth knowing rather than rediscovering. 638 tests. The solution-wide run stays green with the stack down: exit code 8 means "no tests ran", which the platform reports as failure, so the opt-in project ignores exactly that code.
41 lines
2.0 KiB
XML
41 lines
2.0 KiB
XML
<Project Sdk="Microsoft.NET.Sdk">
|
|
|
|
<!--
|
|
M1's definition of done, automated: a real DodoSSH API, a real PostgreSQL, a real Keycloak and a real
|
|
sshd, driven by the real client from sign-in to an interactive shell.
|
|
|
|
Nothing here is stubbed. Every other suite in the repository substitutes something — a stubbed identity
|
|
provider, an in-memory vault server, an in-memory cache — and each of those substitutions is a place a
|
|
misunderstanding of the protocol can hide on both sides at once. This suite exists to catch exactly
|
|
that, and it already has: the realm file registered a loopback redirect URI that Keycloak rejects,
|
|
which no stub would ever have noticed.
|
|
|
|
It needs the development stack up and is skipped otherwise. The commands are in the README under
|
|
"End-to-end verification"; a skipped run prints them too. (They cannot be repeated here: an XML
|
|
comment may not contain a double hyphen, and every one of them has a flag.)
|
|
-->
|
|
|
|
<PropertyGroup>
|
|
<!--
|
|
Exit code 8 is "no tests ran". Microsoft.Testing.Platform reports that as a failure, so an assembly
|
|
whose only test skips would fail the solution-wide `dotnet test` on any machine without the stack up.
|
|
The minimum-expected-tests option cannot express this: it demands a non-zero integer.
|
|
|
|
Narrow enough to be safe here: this project contains exactly one test, so if it runs at all it either
|
|
passes or fails, and 8 can only mean it skipped for want of the stack.
|
|
-->
|
|
<TestingPlatformCommandLineArguments>--ignore-exit-code 8</TestingPlatformCommandLineArguments>
|
|
</PropertyGroup>
|
|
|
|
<ItemGroup>
|
|
<ProjectReference Include="../../src/DodoSSH.Client.Session/DodoSSH.Client.Session.csproj" />
|
|
<ProjectReference Include="../../src/DodoSSH.Client.Ssh/DodoSSH.Client.Ssh.csproj" />
|
|
<ProjectReference Include="../../src/DodoSSH.Client.Terminal/DodoSSH.Client.Terminal.csproj" />
|
|
</ItemGroup>
|
|
|
|
<ItemGroup>
|
|
<PackageReference Include="Testcontainers" />
|
|
</ItemGroup>
|
|
|
|
</Project>
|