docs: clarify CORS (#2283)

* docs: clarify CORS

Closes ory/hydra#3795

* Update docs/hydra/guides/cors.mdx

Co-authored-by: Vincent <[email protected]>

* Update docs/hydra/guides/cors.mdx

Co-authored-by: Vincent <[email protected]>

* Update docs/hydra/guides/cors.mdx

Co-authored-by: Vincent <[email protected]>

* Update docs/hydra/guides/cors.mdx

Co-authored-by: Vincent <[email protected]>

* Update docs/hydra/guides/cors.mdx

Co-authored-by: Vincent <[email protected]>

* Update docs/hydra/guides/cors.mdx

Co-authored-by: Vincent <[email protected]>

* Update docs/hydra/guides/cors.mdx

Co-authored-by: Vincent <[email protected]>

* chore: synchronize workspaces

* Modify CORS settings to use wildcard for origins

Updated CORS configuration to allow all origins for public OAuth2 client registration.

---------

Co-authored-by: Vincent <[email protected]>

Author: aeneasr

docs/hydra/guides/cors.mdx

@@ -1,12 +1,14 @@
 ---
 id: cors
-title: Setting up cross-origin resource sharing (CORS)
+title: Configure cross-origin resource sharing (CORS)
 ---
 
-Both Ory Hydra's Admin and Public endpoints support CORS. For detailed information, head over to the exemplary
-[config file](https://github.com/ory/hydra/blob/master/.schema/config.schema.json).
+Ory services support cross-origin resource sharing (CORS). For the full schema, see the
+[configuration file](https://github.com/ory/hydra/blob/master/.schema/config.schema.json).
 
-For CORS to work properly, we encourage to set the following values:
+## Configure CORS in Ory Kratos
+
+Enable CORS for specific origins in your configuration file:
 
 ```yaml
 serve:
@@ -15,38 +17,43 @@ serve:
       enabled: true
       allowed_origins:
         - https://example.com
-        - https://*.example.com
-      allowed_methods:
-        - POST
-        - GET
-        - PUT
-        - PATCH
-        - DELETE
-      allowed_headers:
-        - Authorization
-      exposed_headers:
-        - Content-Type
+        - https://*.example.com # Wildcards are supported
   public:
     cors:
       enabled: true
       allowed_origins:
         - https://example.com
         - https://*.example.com
-      allowed_methods:
-        - POST
-        - GET
-        - PUT
-        - PATCH
-        - DELETE
-      allowed_headers:
-        - Authorization
-      exposed_headers:
-        - Content-Type
 ```
 
-Keep in mind that the OAuth 2.0 Authorization Endpoint (`/oauth2/auth`) doesn't expose CORS by design. This endpoint should never
-be consumed in a CORS-fashion. Some endpoints (`/oauth2/token`, `/userinfo`, `/oauth2/revoke`) also include URLs listed in field
-`allowed_cors_origins` of the OAuth 2.0 Client that is making the request. For example, OAuth 2.0 Client
+## Configure CORS in Ory Hydra
+
+We recommend the following base configuration:
+
+```yaml
+serve:
+  admin:
+    cors:
+      enabled: true
+      allowed_origins:
+        - https://example.com
+        - https://*.example.com
+  public:
+    cors:
+      enabled: true
+      allowed_origins:
+        - * # Use wildcard for using Ory Hydra in 3rd party scenarios (public OAuth2 client registration), otherwise fixed domains.
+```
+
+### OAuth 2.0 authorization endpoint
+
+The authorization endpoint (`/oauth2/auth`) never supports CORS. Browsers call this endpoint directly, not through AJAX, so CORS
+is unnecessary and unsafe.
+
+### OAuth 2.0 token endpoint
+
+The token, userinfo, and revocation endpoints (`/oauth2/token`, `/userinfo`, `/oauth2/revoke`) allow requests from origins defined
+in the OAuth 2.0 client’s `allowed_cors_origins` field. Example:
 
 ```json
 {
@@ -55,5 +62,81 @@ be consumed in a CORS-fashion. Some endpoints (`/oauth2/token`, `/userinfo`, `/o
 }
 ```
 
-is allowed to make CORS request to `/oauth2/token` from origin `https://foo-bar.com/` even if that origin isn't listed in
+This client can make CORS requests to `/oauth2/token` from `https://foo-bar.com/`, even if that origin isn't listed in
 `public.cors.allowed_origins`.
+
+::: note
+
+For preflight (OPTIONS) requests, you must also configure the origin in the global CORS settings. OPTIONS requests don’t include
+authorization headers, so Hydra can't resolve which OAuth 2.0 client is making the request.
+
+:::
+
+## Configure CORS in Ory Keto
+
+```yaml
+serve:
+  read:
+    cors:
+      enabled: true
+      allowed_origins:
+        - https://example.com
+        - https://*.example.com
+  write:
+    cors:
+      enabled: true
+      allowed_origins:
+        - https://example.com
+        - https://*.example.com
+  metrics:
+    cors:
+      enabled: true
+      allowed_origins:
+        - https://example.com
+        - https://*.example.com
+```
+
+## Configure CORS in Ory Oathkeeper
+
+```yaml
+serve:
+  proxy:
+    cors:
+      enabled: true
+      allowed_origins:
+        - https://example.com
+        - https://*.example.com
+  api:
+    cors:
+      enabled: true
+      allowed_origins:
+        - https://example.com
+        - https://*.example.com
+```
+
+## Advanced configuration
+
+You can customize allowed methods, headers, and other CORS behavior:
+
+```yaml
+cors:
+  enabled: true
+  allowed_origins:
+    - https://example.com
+
+  allowed_methods:
+    - GET
+    - POST
+    - PUT
+    - PATCH
+    - DELETE
+    - OPTIONS
+  allowed_headers:
+    - Content-Type
+  exposed_headers:
+    - Content-Type
+    - Date
+    - Vary
+  allow_credentials: true
+  debug: true
+```