getsentry / getsentry/sentry

SCIM sync of Groups is buggy

Open
#88,623 1 comment 1 reaction 0 assignees View on GitHub
Product Area: Sign In
Dominant language
Python
Stars
44.8k
Forks
4.9k
Avg merge
22h 21m
Merged PRs (30d)
586

Description

### Environment

SaaS (https://sentry.io/)

### Steps to Reproduce

Syncing of group somehow failed by we cannot relink or push the group to Sentry again

```
Getting an error for: SRE:Team
Failed on 04-02-2025 06:37:24PM UTC: Unable to update Group Push mapping target App group SRE:Team: Error while creating user group SRE:Team: Conflict. Errors reported by remote server: A team with this slug already exists.
```

We can’t delete the existing sre-team group, nor does it show up as a group we can link to.

### Expected Result

We can either manually link the team on Okta, or repush the group.

### Actual Result

Getting an error

### Product Area

Sign In

### Link

_No response_

### DSN

_No response_

### Version

_No response_

Contributor guide

Open the contributing guide

Research direction

The issue concerns SCIM group sync in the Sign In area and the failing group-push mapping for SRE:Team; start by reproducing the conflict against the existing sre-team group. Done means an administrator can relink the existing team or repush the group without the “A team with this slug already exists” error.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
authentication
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
30/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.