fix(api): tombstone deleted Auth0 identities - #64
Merged
Merged
Conversation
API unit-test coverage
Unit suite only; controllers are exercised by the e2e suite. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Fixes Problem 2 (JWT resurrection via auto-provisioning) from the account-deletion work in #37. After Auth0-first delete, an unexpired access token could still JIT-create a User for the same providerSub. On hard delete we upsert a DeletedProviderSub tombstone in the same transaction as user.delete; resolveByProviderSub refuses tombstoned (and mid-deletion) identities with a generic 401 so the client learns nothing beyond “unauthorized.” Follows the issue’s tombstone path; deviations: store providerSub plaintext (not hashed), return 401 only (not 410), and keep formerUserId for audit. Event/photo prep remains out of scope.
Resolves #37