Skip to content

tribelt and estate-dashboard sign in through their declared Client #450

Open

Description

@ExtraToast

Parent

#444

What to build

tribelt and the estate dashboard sign in through their declared Client: both declare client and read ${client:secret}. Their copies in secret/auth-api and cluster.sh's client stages are removed.

Acceptance criteria

  • Both sign people in through their Client.
  • secret/auth-api holds no copy of either secret, and cluster.sh has no client stage.

Blocked by

Activity

  1. added
    type: featureNew user-facing or operator-facing capability.
    area: deployhomelab-deploy, deploy-v2, manifests, and rollout flow.
    status: ready-for-agentFully specified; an agent may take it with nobody watching.
    on Oct 15, 2026
  2. ExtraToast commented on Oct 29, 2026

    @ExtraToast
    ContributorAuthor

    Picked up from the ready-for-agent backlog and skipped, because it needs a live step first.

    JorisJonkers-dev/identity#25 is still open and status: ready-for-human. Until identity serves the Issuer host, nothing watches the Client objects, so nothing writes secret/data/<namespace>/<application>/client. If JorisJonkers-dev/tribelt and JorisJonkers-dev/estate-dashboard switched to client and ${client:secret} before then, their next release would reference a Vault path nobody creates and sign-in would break. Today both still read their own copy: tribelt from secret/data/platform/tribelt#oidc.client_secret, the dashboard from secret/data/estate-dashboard-system/sign-in#oidc-client-secret.

    The cluster.sh half of the second criterion already holds: JorisJonkers-dev/estate main has no client stage left. Emptying the copies in secret/auth-api is a production Vault write, so a person has to do it after the cutover.

    Question for the maintainer: should this go back to status: blocked until identity#25 closes? Once it closes, the two project-file PRs are small: add the client block, point OIDC_CLIENT_SECRET at ${client:secret}, and drop the old grant key.

  3. ExtraToast commented on Oct 29, 2026

    @ExtraToast
    ContributorAuthor

    Decision (maintainer, 2026-10-29): not now. Identity's production cutover (JorisJonkers-dev/identity#25) is flipped later, and this waits for it. No worker takes it until then.

  4. added
    status: blockedCannot move forward until an external dependency is resolved.
    and removed
    status: ready-for-agentFully specified; an agent may take it with nobody watching.
    on Oct 29, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    area: deployhomelab-deploy, deploy-v2, manifests, and rollout flow.status: blockedCannot move forward until an external dependency is resolved.type: featureNew user-facing or operator-facing capability.

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions