Skip to content

Authenticated Circuits

Test behind sign-in without turning credentials into product data

Authenticated Circuits are designed for dedicated synthetic accounts, scoped credential leases and fresh browser contexts. Permission denials remain evidence; UxerProof never bypasses them.

Availability: Private beta architecture is implemented and fixture-tested. Customer credentials and external authenticated execution are not enabled until a production secret broker passes review.

What this proves

  • Dedicated identities

    Use purpose-created synthetic accounts with only the permissions required for the authorised journey.

  • Short-lived leases

    Workers receive a workspace-, environment- and Run-bound secret reference that expires instead of a reusable stored password.

  • Fresh browser state

    Every Run starts in an isolated context and destroys its session state when execution ends or is stopped.

  • Redaction boundary

    Sensitive input must be redacted before any screenshot, trace, log or structured evidence crosses persistence boundaries.

The workflow

Bounded from target to evidence

  1. 01

    Verify the target Environment and create a least-privilege synthetic identity.

  2. 02

    Reference the identity in the approved Test Contract; never place its secret in a Circuit definition.

  3. 03

    Lease the secret to one isolated worker for one bounded Run.

  4. 04

    Destroy the browser state and expire the lease whether the journey succeeds, fails or is stopped.