Skip to content

AccessOps v0.2.0 — Departure cases, directory lab and console redesign

Choose a tag to compare

@aman-agarwal6 aman-agarwal6 released this 04 Oct 07:26
193d9ea

AccessOps v0.2 turns an employee or contractor departure into a case with an owner, a four-hour target and a required action for every system the person could still reach. Local access is contained immediately; the case closes only when an independent reviewer accepts the exact evidence packet.

  • Live demo, redesigned: dark and light themes, an urgency-ranked departure queue, one explicit next step per case and fixed labels for each kind of evidence. Synthetic data, no account or paid API.
  • Departure cases in the local lab: Keycloak account disable and removal of every known managed group membership, observed separately; owner statements for external work; independent closure; immutable packet.
  • Optional Samba AD-compatible directory: verified LDAPS, immutable GUID targets, atomic account-flag updates and object-scoped permissions.
  • Local live results (3–4 October 2026): departure cases 18/18; Samba directory case 28/28; new LDAPS and Kerberos logins allowed before (2/2) and denied after offboarding (2/2). Eight failed attempts are retained in the published index.
  • CI for this commit: the signed run passed 255 of 255 backend and integration cases on PostgreSQL 17, and the frontend, policy and secret-scan jobs passed. Deployed-demo check: 17 of 17 checks passed against the deployed site.
  • Signed evidence: provenance and CycloneDX SBOM attestations over the frozen archive for 193d9eab4bca89c34bebdd8f5042ab8d3bfe2f5f. Expected repository aman-agarwal6/AccessOps; signer .github/workflows/release-evidence.yml; source ref refs/heads/main.

The signed archive covers its own CI report. recorded-local-checks.json and published-demo-checks.json have separate origins; local hashes are not signatures. See the verification ledger and verification instructions.

Limits: synthetic data only. No Microsoft or GitHub tenant was contacted; those platforms appear as offline fixtures and owner statements. Samba results do not prove Microsoft AD interoperability. Existing sessions and tickets are not revoked, and MFA and live key rotation were not measured. This is a reference system, not a certification or production deployment.