Cannot push a new group with the old name of a renamed group
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 2.3k
- Forks
- 232
- PR merge metrics
- No merged PRs in 30d
Description
Found a bug? Please fill out the sections below. 👍
Issue Summary
Using scim events with okta. When a group is pushed to samljackson scim directory we create group using the displayName. This is stored in the jackson_store and in the jackson_index. When the group is renamed in okta, then we receive a PUT request with the new name which changes the information in the jackson_store, but the index remains unchanged. Then if I create a group with the old name in okta and try to push it, it conflicts because it uses the index which is by the old name.
Steps to Reproduce
- Go to okta push group (POST)
- Rename group (PUT)
- Create group with old name
- Push the created group.
Contributor 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.
Research direction
Start by tracing the SCIM group POST and PUT handling described in the issue, then follow how renamed groups update jackson_store and jackson_index. Reproduce the Okta sequence and verify that the old name can be used for a newly pushed group without an index conflict.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- nodejs, typescript
- Domain
- authentication, backend-api-design
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100