Pending Invitation Not Cancelled When User Deleted via SCIM
Maintainers usually reply within 2 days
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 55/100
Research direction
Start at the SCIM DELETE /Users/{id} handler and trace how pending invitations are handled when a user is removed. Reproduce the sequence described in the issue, then verify that deletion cancels the pending invitation and prevents the user from reappearing through invitation acceptance.
Written by the indexing model from the issue text.
Description
Summary
When a user is deleted via SCIM before they have accepted their invitation, the pending invitation remains active. The deleted user can still accept the invitation and join the team. The user appears as an active team member but is unable to log in to Wire. This is primarily a visual bug — the user shows up in the team roster but is functionally inaccessible.
Expected behavior
When a SCIM DELETE request is received for a user, any pending invitation associated with that user should be automatically cancelled. The user should not appear as an active team member after deletion, and no invitation should remain that could allow re-joining.
Actual behavior
- User is created and an invitation is sent (user has not accepted yet)
- User is deleted via SCIM
DELETE /Users/{id} - The pending invitation remains active in the system
- The user can accept the invitation and is added back as an active team member
- The user appears in the team roster but cannot log in to Wire
- Dominant language
- Haskell
- Stars
- 2.8k
- Forks
- 332
- Avg merge
- 3d 7h
- Merged PRs (30d)
- 49
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- No contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from wireapp/wire-server
-
Difficulty 1/5 Under an hour Newbie friendliness 83/100
wireapp/wire-server#5632 ·
Maintainers usually reply within 2 days
-
Difficulty 4/5 3-5 days Newbie friendliness 45/100
wireapp/wire-server#5315 · 4 comments · 1 reaction ·
Maintainers usually reply within 2 days
-
Dependency DashboardOpen
Difficulty 5/5 Over a week Newbie friendliness 20/100
wireapp/wire-server#4754 ·
Maintainers usually reply within 2 days
-
Difficulty 5/5 Over a week Newbie friendliness 20/100
wireapp/wire-server#4613 ·
Maintainers usually reply within 2 days
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
wireapp/wire-server#4469 · 1 comment ·
Maintainers usually reply within 2 days
All issues in wireapp/wire-server
Similar issues
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
MorphRule, DataizeRule and ContextualizeRule silently accept unknown YAML keys, unlike rewrite `Rule`Possibly taken @renyamamoto2026-cmyk claimed this 1 day ago. Openbug
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
objectionary/phino#2107 ·
Maintainers usually reply within 1 day
-
30-minutes algorithm any-language codewars dart easy elixir hackerrank hacktoberfest haskell help wanted interview-prep julia leetcode lua open-source r scala students zig
Difficulty 2/5 Under an hour Newbie friendliness 88/100
Huerte/algo-solutions-python#124 ·