Candidate Session Admin

Create candidate sessions with the right lab, seat, and handoff link.

Choose the candidate, lab, Windows seat, and duration. The system queues provisioning, records the injected issues, and gives you a clean candidate link to send.

Candidates see only the controlled browser handoff. The lab topology, injected faults, and reset controls stay on the administrator side.

Admin-facing only Timed session code issuance Windows seat launch URL Hidden GNS3 backend

Session outcome

Candidate-ready handoff

Candidate Name and track tied to one session code

Seat Assigned Windows toolbox VM and reconnect path

Scenario One hidden GNS3-backed problem statement per interview

Portal Login sends the candidate directly to the Windows launch URL

Create Session

Everything needed to put a candidate in the right seat.

Use a browser-based Windows launch URL if you want the candidate to land in the VM immediately after sign-in. This could be an Apache Guacamole link, an RDP web gateway, or another approved reconnect page.

Candidate name Track Scenario Lab type Lab size Randomize issues per candidate (recommended) Seat name RDP target Windows launch URL Duration (minutes) Fault seed (optional) Candidate objective

Issued session

Create a session to issue a candidate code and launch handoff.

Candidate link

Send this URL to the candidate. It is safe to open on their computer (browser only).

Create a session to generate a candidate URL.

Apply to GNS3 (Ops)

Run this on the ops workstation to build the per-candidate GNS3 topology and inject the randomized issues.

Create a session to generate an apply command.

Launch notes

Prefer a browser-based Windows seat launch URL if you want immediate handoff after candidate login.
Keep the hidden GNS3 backend off the public path.
Use one Windows seat per candidate session and reset it after the interview.

Admin broker status: checking configuration.

Ops status: loading...

Seat diag: idle.

Session details

Recent sessions

Quick actions for the last few sessions (re-roll, reset baseline, expire).

Code	Candidate	Lab	Provision	Actions
Loading...

Launch Model

Candidate login should lead straight to the Windows toolbox seat.

Recommended

Browser-accessible Windows seat

Use a Guacamole, Apache Gateway, or other browser-safe reconnect URL.
The portal can redirect immediately after session validation.
The candidate remains on a controlled Windows workstation with the approved troubleshooting tools installed.

Acceptable

RDP or alternate reconnect handoff

Use a launch page, reconnect URL, or downloaded connection file if the environment requires it.
The session API should still return the single assigned target, not a list of infrastructure choices.