Ory is the largest open source community in the world for cloud software application security. We maintain advanced open source security software solving authentication, authorization, access control, application network security, and delegation. Ory implements a variety of industry and best-practice standards including OAuth 2.0 / OAuth 2.1, OpenID Connect, Zero Trust Networking, Google Zanzibar Policy Framework, FIDO2 U2F, WebAuthn, TOTP, and more.

Ory Community

Hi all, I've been scratching my head for ages on this. Is there any reason the CORS headers are not added correctly when querying the token endpoint? Both my client and project configuration include the domain to allow. Everything is hosted by Ory. Using the CLI locally works like a charm for local dev.
`public:`
    `cors:`
      `allow_credentials: true`
      `allowed_headers:`
      `- Accept`
      `- Content-Type`
      `- Content-Length`
      `- Accept-Language`
      `- Content-Language`
      `- Authorization`
      `allowed_methods:`
      `- POST`
      `- GET`
      `- PUT`
      `- PATCH`
      `- DELETE`
      `- CONNECT`
      `- HEAD`
      `- OPTIONS`
      `- TRACE`
      `allowed_origins:`
      `- <https://admin.mydomain.com>`
      `- https://*.<http://mydomain.com|mydomain.com>`
      `debug: false`
      `enabled: true`
      `exposed_headers:`
      `- Cache-Control`
      `- Expires`
      `- Last-Modified`
      `- Pragma`
      `- Content-Length`
      `- Content-Language`
      `- Content-Type`
      `max_age: 0`

`{`
	`"client_id": "a8b4df79-XXXXXXXX",`
	`"allowed_cors_origins": [`
		`"<https://admin.mydomain.com>"`
	`],`
`}`