Secrets, schedules-as-objects, group runs, OIDC UX, installer dialog and GPO polish #2
Reference in New Issue
Block a user
Delete Branch "dev"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Everything since the MVP merge: identity, secrets, scheduling, targeting and installer/GPO polish. 26 commits, all verified locally (169 tests green across shared/agent/backend, Release build, production WebUI build, live screenshot passes against a seeded stack).
Identity & sign-in
/login?local=1,docker exec … Backend.dll auth-reset,AUTH_FORCE_LOCAL=1; SSO-only modes refuse to save while OIDC is unusable./api/auth/oidc/callback(constant-backed, rides the/api/proxy location); redirect URI shown copyable in Settings.OIDC_PROVIDER_NAME/ Settings field; authority host as fallback).Secrets
$Secrets.Name, variable name configurable). Failures are value-free and fail the job before dispatch.Parameters
%VAR%then$env:/$()in the job runspace) with a single Literal opt-out; builder moved to a full-width strip above the editor.Targeting & scheduling
JobRunner(secrets resolved once per fan-out).Devices
Installer & GPO
Infra
PublicUrl.Resolve:PUBLIC_SERVER_URLwins, trusted forwarded headers otherwise — used by the install command, redirect URI andGET /api/settings/server.Note for reviewers
CI
build-testcurrently fails on runnerAPP-DEV-00001withCannot find: node in PATH— the runner host needs Node.js installed and on the service PATH (act_runner requires it for actions/checkout etc.). Not a repo issue; everything passes locally.🤖 Generated with Claude Code
New OIDC_PROVIDER_NAME / Settings field ("Authentik", "Entra ID", …) feeds the sign-in button subtext; the authority host remains only the fallback when no name is set. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>actions/checkout only recognizes 40-hex SHA-1 ids; this repository uses the SHA-256 object format, so the 64-hex head sha was fetched as a named ref ("couldn't find remote ref"). Branch/tag names sidestep it. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>checkout@v4 inits a SHA-1 repository and then fetches, which a SHA-256 server refuses ("mismatched algorithms"). A plain git clone negotiates the object format, so the workflows check out with git + the injected token (branch for pushes/PRs, tag for releases). Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>