mirror of
https://github.com/kevinveenbirkenbach/computer-playbook.git
synced 2026-11-06 19:01:54 +00:00
kevinveenbirkenbachandClaude Opus 5.5
47060a72d3
Follow-up to the v1.0.0 port, closing holes a review and a local run found: - WebUI sign-in: WebUI v2 sends an http:// client-metadata-document id on the onion origin, which Stalwart v1.0.0 rejects (unknown http ids get no CIMD fallback, trusted hosts require TLS). The recovery admin under SSO hit the same wall with the bare id 'stalwart-webui'. Register a public first-party x:OAuthClient 'stalwart-webui' with the WebUI's callback and login URIs on the served origin, and always inject it as the Application's oauthClientId. Native sign-in now shows Stalwart's consent step; test-login-native.js clicks it and also runs under SSO. - Store guard: the previous guard only checked a running 0.16 server; a local run showed v1 writing into a 0.16 store whose server was stopped. The guard now reads the store whenever one exists (shared: pg_database, dedicated: volume) and fails on the 0.16 bigint layout. A host marker written at the end of a successful v1 deploy lets restores and redeploys with a stopped dedicated database pass; without the marker, a stopped dedicated database fails with an explicit message instead of a masked psql error. Queries retry while the database recovers. - README: WebUI sign-in, guard semantics, restore and redeploy. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
5 lines
227 B
Django/Jinja
5 lines
227 B
Django/Jinja
{
|
|
"using": ["urn:ietf:params:jmap:core", "urn:stalwart:jmap"],
|
|
"methodCalls": [["x:OAuthClient/set", {"update": { {{ stalwart_webui_oauth_clients[0].id | to_json }}: {{ stalwart_webui_oauth_client | to_json }} }}, "c0"]]
|
|
}
|