1. The server responded fine — it produced a list of tenants. The problem is purely in how that response is validated, not in the query.
2. The schema's email constraint is stricter than the data. The tenants in this metal-stack test environment have email values that are not RFC-5322-valid email
addresses. Looking at the tenant identifiers we saw in the project data, tenants use names like:
- Ft
- demo
- ftbrm
- metal-stack
- stefan.majer@company@openid-connect
Many of these are plain usernames/logins (e.g. fits, demo) — not email addresses at all. The schema's email format requires something shaped like user@domain. A
bare identifier like fits has no @ and no domain, so it fails format: "email".
Even the ones with @ fail: stefan.majer@company@openid-connect has two @ signs and a non-conforming structure, so it's still not a valid single email
address.
Description