New message text here

New message text here

New message text here

Based on the provided knowledge sources, Ory Oathkeeper’s mutators (such as the

header

mutator) allow you to set headers using Go templates that have access to the

AuthenticationSession

struct. This struct includes fields like

.Subject

and

.Extra

, but the knowledge sources do not explicitly mention a built-in way to distinguish between a user and a client within the mutator template context. Typically, you might differentiate between a user and a client by how the subject is set (e.g., a user ID vs. a client ID), or by including custom claims or extra fields during authentication. If your authentication flow (e.g., via Hydra or Kratos) sets a distinguishing value in the session (such as a claim in

.Extra

), you could use that in your header mutator template:

yaml mutators:   header:     enabled: true     config:       headers:         X-Actor-Type: "{{ if eq .Extra.actor_type \"client\" }}client{{ else }}user{{ end }}"

However, the knowledge sources do not provide a ready-made or automatic way to set such a value; you would need to ensure your authentication process populates

.Extra.actor_type

or a similar field accordingly [Header mutator documentation](https://www.ory.sh/docs/oathkeeper/pipeline/mutator#header). Summary: You can set headers conditionally in the mutator if your authentication process provides a way to distinguish user vs. client in the session data. There is no built-in or automatic mechanism in Oathkeeper for this; you must ensure the relevant information is present in the session for the mutator to use. If you need more details on how to populate

.Extra

or similar fields, the knowledge sources do not provide explicit instructions.

I'm sorry, but the knowledge sources do not contain information about Ory Oathkeeper (or "oauthkeeper") supporting responses in gRPC-Web format. The documentation does mention that Oathkeeper can be used as a gRPC middleware for Go applications, allowing it to handle gRPC traffic directly within a Go application, but it does not specify support for gRPC-Web, which is a protocol for browser-based gRPC communication [Oathkeeper gRPC middleware](https://www.ory.sh/docs/oathkeeper/grpc-middleware). If you require gRPC-Web support specifically, the knowledge sources do not provide enough information to confirm whether this is natively supported by Oathkeeper.