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

I'm not sure if this is just an inconsistency or by design, but would be great to get some clarification (maybe one for <@U03DJ6Q0EUE>)

The <https://www.ory.sh/docs/reference/api#tag/identity/operation/createRecoveryCodeForIdentity|recovery code endpoint> returns both `recovery_code` and `recovery_link` in the response.  However, the templating for Courier, only exposes the `recovery_code` , `recovery_link` is always `null`

Example payload from Courier (using `delivery_strategy: http`
```{
  "name": null,
  "recipient": ""ello@workd.com7755",
  "recovery_url": null,
  "template_type": "recovery_code_valid",
  "to": "<mailto:hello@world.com|hello@world.com>",
  "verification_url": null
}```

This is deliberate, because the self-service recovery sets anti-CSRF tokens during the flow, which means that accessing the flow from e.g. a different browser, or doing something in between, will result in the flow failing.

In the admin endpoint we deliberately disable the CSRF protection, because we assume that the admin would do the verification of the user (e.g. they are making sure the user is actually the owner of the account), making a CSRF attack unlikely to impossible.

That makes sense, thanks for the clarification!