loud-restaurant-89371
03/11/2025, 11:34 PM- OAUTH2_TOKEN_HOOK_AUTH_TYPE=api_key
- OAUTH2_TOKEN_HOOK_AUTH_CONFIG_IN=header
- OAUTH2_TOKEN_HOOK_AUTH_CONFIG_NAME=foo
- OAUTH2_TOKEN_HOOK_AUTH_CONFIG_VALUE=bar
My webhook is being called, but without the specified header. changing the AUTH_TYPE to somethign else does yield an error, so hydra is parsing the config, at least that one. There is no validation on the other three parameters, so I cannot test whether they are correctly parsed or not. Did I make a typo?brief-egg-61061
03/11/2025, 11:34 PMbrief-egg-61061
03/11/2025, 11:35 PMoauth2/token_hook/url
without auth
config: [GitHub Issue: Cannot set oauth2/token_hook/url
without auth
config](https://github.com/ory/network/issues/357) Your configuration appears to be correct based on the documentation format for API key authentication in webhooks: hook: web_hook config: auth: type: api_key config: name: Authorization value: { API Key value } in: header # alternatively "cookie"
As described in [Trigger custom logic and integrate with external systems with webhooks](https://www.ory.sh/docs/guides/integrate-with-ory-cloud-through-webhooks#request-authentication) The fact that changing AUTH_TYPE yields an error but your webhook is called without the header suggests that while the configuration is being parsed, the authentication implementation might not be working correctly for OAuth2 webhooks specifically. This appears to be a known issue rather than a typo in your configuration. If you need this functionality urgently, you might want to check if there have been any updates to Hydra since these issues were reported or reach out to the Ory community on Slack for the latest status.