Allow custom URI schemes for CORS allowed origins
Nessuno ha ancora preso questa issue.
Valutazione
- Difficoltà
- 4/5
- Tempo stimato
- 3-5 giorni
- Idoneità per principianti
- 55/100
- Tipo di issue
- Funzionalità
- Chiarezza
- Abbastanza chiara
- Stato di attività
- Attiva
- Stack tecnologico
- ios
- Ambito
- api, mobile-dev, security
Direzione di ricerca
Start by tracing validation and matching for cors_allowed_origins on custom domains, then compare it with the redirect URL handling implemented for issue #331. Done means custom URI schemes such as capacitor:// are accepted with exact matching, while existing http and https behavior remains unchanged; verify the preflight behavior and relevant validation tests.
Scritto dal modello di indicizzazione a partire dal testo della issue.
Descrizione
Preflight checklist
- I could not find a solution in the existing issues, docs, nor discussions.
- I agree to follow this project's Code of Conduct.
- I have read and am following this repository's Contribution Guidelines.
- I have joined the Ory Community Slack.
- I am signed up to the Ory Security Patch Newsletter.
Ory Network Project
https://thirsty-wozniak-lyfkkuj3wq.projects.oryapis.com
Describe your problem
The CORS allowed-origins validator on a custom domain accepts http and https only. Any other scheme is rejected with:
'capacitor://app.example.com' is not a valid CORS origin. Use '<scheme>://<hostname>:<port>'.
The message points at the format, but the format is not the issue — the scheme is. Tested on our project, on Branding → Custom domains → Allowed origins:
| origin | result |
|---|---|
https://app.example.com |
accepted |
http://app.example.com |
accepted |
capacitor://app.example.com |
rejected |
capacitor://app.example.com:443 |
rejected, same message — so it is not about the port |
myscheme://app.example.com |
rejected — so it is not about capacitor specifically |
This locks out hybrid mobile apps on iOS.
A Capacitor/Ionic app serves its bundled WebView from a custom scheme, and that is the Origin the WebView sends: capacitor://localhost by default, or capacitor://<your-hostname> once server.hostname is configured. Since that origin cannot be allow-listed, a plain fetch() from the app to Ory is impossible on iOS (the preflight is never granted).
The scheme is not negotiable on our side either. Capacitor's iosScheme cannot be set to http or https, because WebKit raises on it.
So there is no scheme that satisfies both Ory and iOS.
Android is unaffected :androidScheme defaults to https, and after adding https://<our-host> to the custom domain's allowed origins, the full flow works (preflight 204 with access-control-allow-headers: authorization, then GET /sessions/whoami returning 200 with the tokenized session). Only iOS is stuck.
Describe your ideal solution
Allow custom URI schemes in cors_allowed_origins on custom domains, with exact matching only (no wildcard support needed for them).
There is a direct precedent: #331 raised the same limitation for redirect URLs and was implemented. The same reasoning applies here, for the same class of application.
Workarounds or alternatives
-
Bypass the browser with a native HTTP plugin. This is what Capacitor's own documentation recommends when CORS blocks you, and it is what we do today. It works, but it moves the request out of the WebView's network stack and into the platform's raw HTTP client, losing Happy Eyeballs, the browser's DNS resolver, connection pooling and coalescing.
-
Run a backend proxy that forwards to Ory server-side, so the app talks to an origin we control. This works, and it is our fallback, but it means standing up and maintaining a service whose only purpose is to relay auth calls (which rather defeats the point of a managed identity provider).
Version
Ory Network (managed), as of 2026-09-30
Additional Context
No response
- Lingua principale
- Shell
- Stelle
- 96
- Fork
- 8
- Metriche di merge delle PR
- Nessuna PR unita negli ultimi 30g
Preparare l'ambiente
Come iniziare
- Leggi tutta la issue e poi la guida ai contributi del progetto.
- Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
- Fai un fork del repository e lavora su un branch.
- Apri una pull request che faccia riferimento al numero della issue.
Altre issue di ory/network
-
bug
Difficoltà 4/5 3-5 giorni Idoneità per principianti 38/100
-
Updating native registration flow with OIDC ID token for existing identity returns breaking responseApertabug
Difficoltà 4/5 3-5 giorni Idoneità per principianti 35/100
-
Ory Account Experience (hosted UI) registration trait setup via creation of registration flowApertafeat
Difficoltà 5/5 Più di una settimana Idoneità per principianti 25/100
-
selfservice.flows.login.style reverts to identifier_first despite explicitly setting passwordApertabug
Difficoltà 4/5 3-5 giorni Idoneità per principianti 30/100
-
feat
Difficoltà 5/5 Più di una settimana Idoneità per principianti 35/100
Issue simili
-
Bug: pane path not quotedApertabug
Difficoltà 2/5 1-3 ore Idoneità per principianti 67/100
-
Does a subagent definition's `tools:` bypass the permission check? One default-permission cellAperta
Difficoltà 2/5 1-3 ore Idoneità per principianti 72/100
pearu/agent-sandbox#156 ·
I maintainer di solito rispondono entro 1 giorno
-
area/documentation squad/marvin
Difficoltà 1/5 Meno di un'ora Idoneità per principianti 90/100
rancher/stackstate-product-docs#443 ·
I maintainer di solito rispondono entro 1 giorno
-
Request: Remove Sikka appAperta
Difficoltà 2/5 1-3 ore Idoneità per principianti 84/100
getumbrel/umbrel-apps#6142 ·
I maintainer di solito rispondono entro 2 giorni
-
triage/confirmed
Difficoltà 2/5 1-3 ore Idoneità per principianti 78/100
agentscope-ai/agentscope#3030 ·
I maintainer di solito rispondono entro 1 giorno