ory / ory/network

Recovery emails are sent to inactive identities

Open
#360 0 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

bug
Dominant language
Shell
Stars
96
Forks
8
PR merge metrics
No merged PRs in 30d

Description

Preflight checklist
Ory Network Project

No response

Describe the bug

If an inactive identity goes through the Recovery flow, they receive the recovery email with the code in it. After submitting the code, they receive a "message":"identity is disabled","reason":"This account was disabled." unauthorized/401 error.

I feel like they shouldn’t receive the email with the code. If Notify unknown recipients is enabled, then perhaps inactive identities would receive that email instead.

Reproducing the bug
  • PATCH an existing identity so that it has state: 'inactive' (ensure you have access to this identity's email)
  • Go to the Recovery page, and submit the email of the inactive identity
  • Wait for the email to be delivered and copy the recovery code from the email
  • Submit the recovery code form
Relevant log output

No response

Relevant configuration

No response

Version

Ory Network

On which operating system are you observing this issue?

Ory Network

In which environment are you deploying?

Ory Network

Additional Context

No response

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reproducing the flow with an identity patched to state inactive, then trace the Recovery page, recovery email, and code-submission path. Compare the behavior with the Notify unknown recipients setting; done means inactive identities do not receive a usable recovery code and the intended notification behavior is covered by tests.

Written by the indexing model from the issue text.

Assessment

Domain
authentication, security
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.