---
title: "2026-09-08 OpenEDC password authentication PR"
description: "Replaced browser-extracted Supabase sessions in vxData jobs with 1Password-injected OpenEDC email/password authentication."
image: "https://docs.virdx.dev/img/virdx-social-card.png"
---

> Documentation Index
> Fetch the complete documentation index at: https://docs.virdx.dev/llms.txt
> Use this file to discover all available pages before exploring further.

# 2026-09-08 OpenEDC password authentication PR

## Work Done

- Opened `virdx/mono` PR [#375](https://github.com/virdx/mono/pull/375).
- Changed `OpenEdcClient` to fetch the public Supabase connection configuration from Confimedis `/api/status` and sign in with email/password.
- Changed the Essen-01 pull and OpenEDC model generator to require `OPENEDC_EMAIL` and `OPENEDC_PASSWORD`.
- Surgically replaced the obsolete browser credential extraction paragraph with an `op run` example.
- Removed the old token and Supabase-key interfaces rather than retaining transitional compatibility.

## Lessons Learned: Pitfalls

- `client.py` still uses `json` for table value normalization, so removing the token JSON parser did not make the module-level `json` import obsolete.
- The vxData jobs pre-commit hook mutates an unrelated `pixi.lock` Python requirement entry while running Pixi tasks. That generated change was restored before push.
- The user explicitly requested no tests. Repository pre-commit hooks still automatically ran formatting, lint, and type checking; no test or live OpenEDC command ran.

## Lessons Learned: Improvements

- For narrow credential migrations, search all uses of an import before removing it, even when the main feature that introduced the import is deleted.
- Authentication docs should use only secret references and runtime injection. They should not instruct users to inspect browser storage or network headers.

Source: https://docs.virdx.dev/knowledge/inbox/2026-09-08-infrastructure-openedc-password-auth-pr/index.mdx