Skip to content

365Lantern 0.1.0-alpha.3 — Authentication reliability

Pre-release
Pre-release

Choose a tag to compare

@NVZLAB NVZLAB released this 13 Oct 20:40
· 1 commit to main since this release
f10d2ad

Authentication reliability

  • Reuse the Exchange connection across read-only collection phases. A failed Exchange authentication attempt is not automatically repeated by later checks; clear/reconnect explicitly to retry.
  • Keep Connect tenant responsive while the helper starts, with Cancel visible on that screen and during collection.
  • Add Use a browser sign-in code on Connect tenant. If the normal sign-in window does not appear, cancel, enable this option and retry. Lantern displays the short-lived code and a fixed Microsoft sign-in link. Existing browser windows can stay open. Graph and Exchange each authorize their own service; sign in with the same administrator account.
  • Handle default-browser launch failure without crashing; the Microsoft URL can be opened manually.

Security and limits

Graph and Exchange have separate service tokens, so this does not guarantee a single prompt. Tenant consent, MFA and Conditional Access can still require interaction or prohibit device-code flow. Response actions retain separate, action-specific authorization. Codes are cleared after completion/cancellation/disconnect and are never added to exports; Lantern does not add persistent credential storage.

Validation

442 automated checks passed, including one Exchange authentication across phases, no automatic retry after a failed connection, device-code forwarding/clearing, and termination of stalled authentication. Packaged UI smoke tests and downloaded-helper startup checks passed. Automated authentication checks use synthetic modules. The maintainer then tested the replacement application live: normal sign-in and investigation succeeded with one additional browser sign-in during collection. Cancel also worked. Device-code flow was denied by Microsoft in the test tenant (530035); leave that option unchecked when tenant policy blocks it. The installer wraps the same tested application payload.

Download the unsigned per-user Setup.exe and its SHA-256 checksum below. No administrator elevation is required; Windows may show an unknown-publisher warning. Export your investigation before closing the old app and installing the update.