LeoVasanko 52f3b26630 Wildcard origins follow the shell-glob convention: **. for apex+any depth, *. for one level ...

'**.example.com' covers the apex and subdomains at any depth;
'*.example.com' covers exactly one subdomain level (neither apex nor
deeper) — analogous to permission scope wildcards, and sidestepping the
DNS/TLS/nginx ambiguity around '*.'. This also allows excluding the apex
where wanted. The seeded/default entry becomes '**.{rp-id}' (init,
add-domain, legacy empty-origins conversion, branch-era '*' sanitize
rewrite).

2026-09-07 15:15:30 +00:00

..

__init__.py

API tests added with near-complete coverage over user and admin APIs. 60% overall backend. (not including E2E test in coverage)

2025-12-06 04:45:26 +00:00

conftest.py

Wildcard origins follow the shell-glob convention: **. for apex+any depth, *. for one level

2026-09-07 15:15:30 +00:00

test_admin.py

Wildcard origins follow the shell-glob convention: **. for apex+any depth, *. for one level

2026-09-07 15:15:30 +00:00

test_api.py

Tests: align with instance-global OIDC and per-domain auth hosts

2026-09-07 06:33:54 +00:00

test_cli.py

Wildcard origins follow the shell-glob convention: **. for apex+any depth, *. for one level

2026-09-07 15:15:30 +00:00

test_domains.py

Wildcard origins follow the shell-glob convention: **. for apex+any depth, *. for one level

2026-09-07 15:15:30 +00:00

test_user.py

Test suite for the realm architecture

2026-09-06 04:28:35 +00:00