Sure, here is an example of a valid YAML configuration for Ory Oathkeeper access rules:

yaml - id: "ws:protected"     upstream:       preserve_host: true       url: "<http://ws:8080>"     match:       url: "<http://127.0.0.1:8080/<**>>"       methods:       - GET       - POST     authenticators:       - handler: cookie_session     mutators:       - handler: noop     authorizer:       handler: allow     errors:       - handler: redirect         config:           to: <http://127.0.0.1:4455/login>

This configuration uses the [cookie authenticator](https://www.ory.sh/docs/oathkeeper/pipeline/authn#cookie_session) against Ory Kratos and proxies only authenticated requests to

<http://ws:8080>

upstream. The

ws

hostname is resolved through the Docker network. If you aren't deploying your application within Docker, this would just be your localhost IP. You can find more examples and detailed information about the access rules in the [Ory documentation](https://www.ory.sh/docs/oathkeeper/api-access-rules#examples).

New message text here

@chilly-king-10285 Could you share a valid yaml configuration for Oathkeeper with multiple access rules?

New message text here

Looks more like what you asked for?