Skip to content

Add private client sign-in and contact onboardingΒ #3936

Open
6 of 9 issues completed
Open

Description

@devantler

πŸ€– Generated by the Agentic Engineer

Current identity scope β€” 23 October 2026

The maintainer has selected Portal β†’ dedicated customer Dex β†’ self-hosted ZITADEL for invited local accounts first, replacing the initial Keycloak preparation. Public self-registration and social connectors stay off. Google, Microsoft, Apple and GitHub are future additions through ZITADEL or Dex after separate protocol, enrollment and identity-linking review; their application registrations are no longer prerequisites for the first release.

business-site #302 owns this identity delivery; its first source-preparation child is #303, implemented in existing PR #304. All business-specific identity source remains in business-site. ZITADEL owns passwords, MFA and recovery; the portal continues to authorize invitations, current membership and customer/operator separation using the Dex issuer and subject. Never join accounts by email or reuse infrastructure identity. The initial scope uses supported embedded Login V1 without a separate Node login workload; validate the real native chain and complete resource footprint, not a language-based memory assumption.

This is a rescope, not activation clearance. Private configuration, signed deployment, actual invitation delivery/MFA/recovery, the real ZITADEL β†’ Dex β†’ portal journey, two-client/operator isolation and the recovery/cutover/privacy gates under #3939 must still pass before opening access. No paid enrollment, real account or production activation follows from this issue update.

Historical delivery observations β€” 21 October 2026

The selected public frontend is now Svelte; ADR 0017 retains Go for private portal presentation. Do not restart the rejected private Svelte experiment or create another portal repository. The older Astro foundation and October 14 delivery observations below are historical, not the current frontend or a new launch clearance.

The 21 October source and live-receipt reads agreed on business-site main 1d34013bb6d40dbf1736c21d677734fe27bfc982, published by the source-owned workflow run 39603006628. All four workflows at that source succeeded. This was public-site publication evidence for that revision, not a current receipt or deployed portal authentication/customer activation.

The immediate deployment predecessor is Platform #5163, under #4854: the maintained WebApp needs bounded startup arguments, non-root workload identity and a compatible private-file projection. PR #5196 establishes actual pinned-KRO compiler/API validation; its final repaired head has green CI but still requires substantive review and protected delivery. Compiler proof alone does not supply controller reconciliation, kubelet projection, a deployed business runtime, database recovery or real-provider proof. Business-site #102 remains held on this deployment path.

Keep this parent open. The historical Google/Microsoft launch requirement is superseded by the current local-account scope above; real configured-broker sign-in, two-client/operator deployed isolation, privacy/retention and the recovery/cutover criteria remain required. Merged default-off source, fictional fixtures and a public-site receipt do not satisfy them.

User Story

As an invited client, I want to sign in with my administered Devantler Tech account and maintain my own contact details, so that I can return securely and Devantler Tech can reach me about a request without exposing another client's information.

First independently shippable portal slice

The maintainer has selected public application source, invitation-only initial access and dedicated customer Dex backed initially by self-hosted ZITADEL. The portal consumes only the configured Dex OIDC issuer. Future social connectors belong in ZITADEL or Dex, not separate authentication implementations inside the app. Customer access remains separate from infrastructure/operator access. #3935 records the earlier foundation choices; business-site#302 owns the current identity scope and #4019 the common frontend standard.

The first slice is real identity and private contact onboarding, not the complete order/payment/agent queue. It should establish a reviewable application foundation and prove its access boundary before collecting real customer data. The existing local prototype is a workflow mockup, not authentication or isolation evidence.

Selected first-slice implementation

Ownership: implement within devantler-tech/business-site, following the maintainer's unified-product decision in #3935. One runtime artifact will serve the selected public frontend and protected /portal routes. Share the public theme/assets and navigation rather than maintaining a second site. Keep private records and server-only material outside the public build/preview/receipt, reject unsafe static fallbacks, and prevent public caching of authenticated responses. The existing Pages site remains live until the reviewed combined runtime cutover; this slice does not enable it.

The bounded foundation decision in #3935 selects one Go application with context-escaped, server-rendered HTML and accessible forms, backed by PostgreSQL for client records, access membership, migrations, login attempts and opaque server-side sessions. Use pgx for PostgreSQL access, maintained go-oidc/OAuth2 components for the single configured broker, and SCS with a PostgreSQL session store. The default in-memory session store is not a production option. Pin and review exact runtime/component versions, transitive licenses and notices during implementation; this issue does not authorize dependencies from an unreviewed example.

Consume broker identities by issuer and subject. Atomic database-backed consumption of each login attempt and invitation must prevent concurrent callback/redemption replay; consuming a value only in one request's session object is not adequate evidence. Session renewal, expiry, revocation and logout must be proved through the actual application handler and durable store.

Select and test the maintained CSRF mechanism before adding any state-changing handler. Include negative controls for unsafe cross-origin requests and requests without Origin/fetch-metadata headers; Go's cross-origin header checks alone do not establish token-based protection for every browser request. No blanket bypass is allowed for contact forms, invitations or account linking.

Keep one application artifact and one dedicated logical database role for this slice. No additional Redis service, frontend server, billing engine, queue service or paid enrollment is needed by the selected foundation itself. This is not proof of available hosting capacity, database isolation, recovery, cost or production readiness; those remain #3939's measured deployment gates.

This is a scope-specific foundation decision, not a benchmarked claim that Go is the best frontend stack across the portfolio. #4019 retains the comparative frontend work. #3935 is now closed with its bounded implementation decision and cost-approval process recorded. Remaining payment comparisons stay with #3937/business-site#21 and do not authorize enrollment. The maintainer approved one default-off portal-foundation PR exception; current WIP limits and every broader release criterion below otherwise remain unchanged. This does not enable real customer intake.

Acceptance Criteria

  • Extend the existing public devantler-tech/business-site source with the private application module under server/, its maintenance instructions, selected stack/license, locked toolchain, RED/GREEN commands, CI and combined immutable artifact through the normal signed/reviewed path. Preserve the source-owned selected public frontend and retained-Go private presentation; do not bootstrap a separate portal repository or restart a rejected rewrite. Application source visibility never makes customer records, fixtures with real data or credentials public.
  • Use dedicated customer Dex backed by maintained self-hosted ZITADEL for invited local accounts. Disable public user/organization registration and social connectors initially; require verified-email credential setup, MFA and bounded recovery. No portal password store, custom identity provider or provider SDKs. Configure private client credentials and exact callbacks; deferred Google/Microsoft/Apple/GitHub registrations are not first-release blockers and are not advertised as working.
  • Use maintained OAuth/OIDC/session components with server-side issuer, signature, audience and expiry validation; transaction-bound authorization code flow with state, nonce and PKCE; allow-listed redirects; secure expiring sessions, rotation/revocation and logout. Pin and review the actual component versions rather than treating a documentation example as the full security implementation.
  • Enforce invitation-only access on the server. Invitations are bounded, expiring, revocable and single-use; concurrent redemption cannot grant two accounts. Bind the authenticated account by the broker issuer/subject and a stable internal client identity, not a browser role or a matching email. Explicit account linking requires authenticated proof of both identities; provider/email changes cannot create a second free entitlement or silently merge customers.
  • Collect only necessary name/contact email and company context; phone is optional unless the agreed workflow establishes a need. Handle contact verification and changes explicitly. Store contacts and access membership durably with migrations and restart behavior; no in-memory customer store or localStorage-only authorization.
  • Authorize every contact read/update on the server. A client can access only its own records; operator capabilities are explicitly assigned and independently checked, never inferred from provider choice or a client-supplied field. Deny by default across UI and API. Customer sign-in grants no platform or agent-execution access.
  • Introduce a default-off release gate and test enabled, explicit false and entirely unset configurations. Disabled mode exposes no sign-in callback, invitation redemption, contact intake or private record endpoints; fail closed when broker/storage configuration is missing or invalid. Health endpoints reveal no credentials or customer state. Synthetic test identities cannot become production fixture logins.
  • RED/GREEN controls cover forged/expired/wrong-issuer/wrong-audience tokens, callback replay, state/nonce/PKCE rejection, session fixation/CSRF and logout, invitation expiry/revocation/double redemption, email collisions/account linking, two-customer cross-record denial and operator impersonation. Exercise concurrent requests, restart persistence and migration behavior. Test the actual application boundary, not only a helper that production does not invoke.
  • Provide accessible EN/DA sign-in/contact/unavailable/error states in the business site's visual language. Verify native keyboard focus and submission, narrow mobile layout and System/Light/Dark. Preserve the measured frontend decision under Select an evidence-backed frontend standard across the portfolioΒ #4019; a polished mockup or popularity ranking is not proof of the chosen stack's suitability.
  • Publish accurate confirmed business/contact and processing/retention information before real customer collection. Devantler Tech's confirmed CVR is 46830385 and contact is ned@devantler.tech; Publish verified company and contact details from business-siteΒ #3917 retains remaining scope. Do not publish the private address, invent VAT/terms or claim compliance from registration alone.
  • Obtain a substantive current-head review, settle the full required CI surface and merge without bypass. Then prove real ZITADEL β†’ customer Dex β†’ portal login/logout, invitation/MFA/recovery and revoked-account behavior with two isolated synthetic clients and an operator at the deployed revision under Deploy and verify the unified business site and private portalΒ #3939. Keep this parent OPEN on missing deployment, private inputs, privacy, recovery or real-chain proof. Verifying is reserved for an actual post-merge check that can run now; a wait-only item retains a recorded resume condition rather than premature Done. Do not claim fixtures are deployed federation.

Dependencies, priority and boundaries

Fresh 14 October 2026 read: native prerequisite #3935 is CLOSED; implementation children business-site#33, #40, #49 and #73 are CLOSED. The old draft-#35 description is superseded: current business-site main 70f10d274a22aacc45f6ef6ad68c3c2a0c9602fb contains browser identity, durable sessions/contact profiles and the combined runtime. Its CI run 38545837816 completed actual database, package/container tests and signed container publication; its source-owned Pages receipt names run 38545837769. Neither artifact publication nor child closure proves a deployed private portal.

Business-site#90 / PR #91 is now CLOSED/MERGED after the normal protected exact-head squash. Actual signed source is 865d882510a69628268d28d52b33788237e95b40; post-merge completion controls and all four merged-source workflows pass, including CI 38560933650 and source-owned Pages 38560933710. The live source receipt matches. This delivers private-read checkpoint hardening, not production portal activation. Keep this parent OPEN for real Google/Microsoft broker configuration, contact verification, processing/retention, deployed client/operator isolation and #3939's recovery/cutover proof. Historical one-PR capacity exceptions do not confer future authority; the maintainer's WIP waiver is confined to the current interactive session. Ownership, review, security, CI and protected merge gates remain unchanged.

Priority: P1 High, maintainer-directed next portal delivery after the business-site publication bridge. This unlocks #3937's customer ownership boundary and reduces the risk of collecting data behind a simulated login. Delivery size: Medium, including tests, CI, review, deployment configuration and actual provider/isolation proof; do not infer a launch date from queue position.

Requests/orders, quote acceptance, operator-confirmed credited bank transfers and worker claims stay under #3937/business-site #20. No paid work, payment collection, agent powers, public website routing or booking is enabled by this identity slice. #3939 owns the unified runtime and recovery proof; #3940 owns the final public handoff. Any proposed paid service must include costs and receive approval before enrollment, as the maintainer confirmed on #3935.

Part of #3934. No passwords, tokens, customer details, private infrastructure topology or raw operational logs in public evidence.

Activity

  1. added theissue type on Oct 7, 2026
  2. added a commit that references this issue on Oct 9, 2026
  3. self-assigned this
    on Oct 9, 2026
  4. added a commit that references this issue on Oct 9, 2026
  5. added a commit that references this issue on Oct 9, 2026
  6. updated Priority High and Effort Medium on Oct 9, 2026
  7. devantler commented on Oct 11, 2026

    @devantler
    ContributorAuthor

    πŸ€– Generated by the Agentic Engineer

    Merged implementation outcome: business-site PR #43 was normally protected squash-merged on 11 October 2026 at source revision b9c18d9396a881510c0eafd80d68bce9153044f2. Login/session child #40 is CLOSED and its board item is Done. The approved one-PR login capacity exception is consumed.

    The unified business-site source now includes actual broker-based browser sign-in/callback/logout, durable PostgreSQL sessions, invitation-only current-membership authorization, a separately authorized operator shell and accessible EN/DA forms. Current-head Codex review was clean; both CodeRabbit findings were root-fixed and resolved. Promotion CI 38097656522 passed the actual database/security suite and public/private build boundary before merge. Browser proof uses explicitly fictional clients and a synthetic broker, not live federation.

    This parent stays OPEN. Still outstanding: privately configured broker Google/Microsoft connections and real-provider proof; combined runtime/ingress and recovery under #3939; authorized contact collection/verification/update and two-client record isolation; processing/retention information and legal/privacy prerequisites in business-site#19/#21. No production portal flag, customer intake, payment, queue, MCP or agent access was enabled. The existing Pages publisher still publishes only public static output, not the Go application.

    Source merge is delivered implementation value, not a production portal launch. Source-owned public publication run 38097875965 completed successfully, with successful exact-source build and protected Pages deployment. The actual https://devantler.tech/publication-source.json receipt names business-site, source revision b9c18d9396a881510c0eafd80d68bce9153044f2 and run 38097875965, attempt 1, publish mode. Actual browser visits verified EN/DA Home and Projects, Journal navigation and native Enter to a reading page. Production portal, sign-in and callback routes return 404. Merged-main CI 38097875927 also completed successfully. Further implementation needs fresh normal downstream capacity or another specific exception, not reuse of this one.

  8. added a commit that references this issue on Oct 13, 2026
  9. devantler commented on Oct 22, 2026

    @devantler
    ContributorAuthor

    πŸ€– Generated by the Agentic Engineer

    Activation check, 22 October 2026: the maintainer has explicitly requested portal activation. Prioritize the existing invitation-only identity/contact launch; this does not enable orders, payments or agent execution.

    Fresh platform main bc8c946c0351bdfce8fd9e2360ff8dd560869796 contains no business-site tenant registration. Its maintained broker configuration selects only the existing administrative connector, corroborated by its operator documentation. This is source evidence, not a live federation test. Customer Google/Microsoft registration and real deployed proof remain unfulfilled; do not weaken administrative access restrictions to make customer sign-in work.

    The source-owned signed deployment release under business-site #102/#276 remains the immediate delivery path. Its archive-admission PR #280 now has a signed repair with 305 complete ordinary Go tests, both actual database integrations, retained guard-removal controls and complete quality checks passing; fresh hosted CI/review are in progress. The current production-template package additionally passes actual executable/public-route/private-route controls with fictional disclosure input. These local checks are not deployment or activation evidence.

    Keep this parent open until the source-owned release and reviewed platform consumption land, private broker/client and restricted database inputs are configured, restart/recovery succeeds, and real Google/Microsoft login/logout plus two-client/operator isolation pass at the deployed source. Keep provider/customer details and credentials out of public evidence. No live setting, account, customer record or production route was changed by this check.

  10. devantler commented on Oct 22, 2026

    @devantler
    ContributorAuthor

    πŸ€– Generated by the Agentic Engineer

    Maintainer configuration fact confirmed in this interactive session on 22 October 2026: the Google and Microsoft application registrations have not been created yet. Do not carry them forward as configured or ask the same factual question again.

    The agreed architecture remains one federated broker consumed through OIDC by the unified business-site application, not individual Google/Microsoft integrations in the portal. Configure registrations and credentials privately, keep customer access separate from infrastructure administration, and verify the actual deployed sign-in/logout and two-client/operator isolation before activation. No credentials belong in chat, issues, source, artifacts or screenshots.

    This fact does not block the independent signed-runtime publication work under business-site#276/#102. It also does not supply provider, deployment, privacy, recovery or launch acceptance. No provider registration, paid enrollment, customer access or production change was made by this record.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

No labels
No labels

Fields

Priority

High

Start date

None yet

Target date

None yet

Effort

Medium

Projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions