[GH-ISSUE #4724] [Bug]: Tenant group member identifier inconsistent - causing mismatch in UI #2201

Closed
opened 2026-03-02 13:50:24 +03:00 by kerem · 6 comments
Owner

Originally created by @PeterVive on GitHub (Sep 29, 2025).
Original GitHub issue: https://github.com/KelvinTegelaar/CIPP/issues/4724

Originally assigned to: @Zacgoose on GitHub.

Required confirmations before submitting

  • I can reproduce this issue on the latest released versions of both CIPP and CIPP-API.
  • I have searched existing issues (both open and closed) to avoid duplicates.
  • I am not requesting general support; this is an actual bug report.

Issue Description

  1. Go to Tenant Administration -> Administration -> Tenants -> Groups (tab).
  2. Find any tenant group and select "Edit group".
  3. Add a tenant to the group.
  4. Go to Tenant Administration -> Administration -> Tenants and select "Edit tenant" on the tenant you just added to the group.
  5. Add the tenant to a group under "Edit tenant properties" on that page, and click "Save".

After refreshing the second tenant group will not appear in the list together with the first one.

Environment Type

Sponsored (paying) user

Front End Version

8.4.2

Back End Version

8.4.2

Relevant Logs / Stack Trace

I believe this occurs because in the Edit Tenant page it uses the tenantId when submitting.
On the Edit Tenant Group page is uses the defaultDomainName.

This results in mixed records in the tables, and a lot of weirdness.

Not sure how to solve - but this appears to be the issue.
Originally created by @PeterVive on GitHub (Sep 29, 2025). Original GitHub issue: https://github.com/KelvinTegelaar/CIPP/issues/4724 Originally assigned to: @Zacgoose on GitHub. ### Required confirmations before submitting - [x] **I can reproduce this issue on the latest released versions** of both CIPP and CIPP-API. - [x] **I have searched existing issues** (both open and closed) to avoid duplicates. - [x] I am **not** requesting general support; this is an actual bug report. ### Issue Description 1. Go to Tenant Administration -> Administration -> Tenants -> Groups (tab). 2. Find any tenant group and select "Edit group". 3. Add a tenant to the group. 4. Go to Tenant Administration -> Administration -> Tenants and select "Edit tenant" on the tenant you just added to the group. 5. Add the tenant to a group under "Edit tenant properties" on that page, and click "Save". After refreshing the second tenant group will not appear in the list together with the first one. ### Environment Type Sponsored (paying) user ### Front End Version 8.4.2 ### Back End Version 8.4.2 ### Relevant Logs / Stack Trace ```plaintext I believe this occurs because in the Edit Tenant page it uses the tenantId when submitting. On the Edit Tenant Group page is uses the defaultDomainName. This results in mixed records in the tables, and a lot of weirdness. Not sure how to solve - but this appears to be the issue. ```
kerem 2026-03-02 13:50:24 +03:00
  • closed this issue
  • added the
    bug
    label
Author
Owner

@github-actions[bot] commented on GitHub (Sep 29, 2025):

Thank you for reporting a potential bug. If you would like to work on this bug, please comment:

I would like to work on this please!

Thank you for helping us maintain the project!

<!-- gh-comment-id:3348583237 --> @github-actions[bot] commented on GitHub (Sep 29, 2025): Thank you for reporting a potential bug. If you would like to work on this bug, please comment: > I would like to work on this please! Thank you for helping us maintain the project!
Author
Owner

@Zacgoose commented on GitHub (Sep 30, 2025):

I would like to work on this please!

<!-- gh-comment-id:3354125792 --> @Zacgoose commented on GitHub (Sep 30, 2025): I would like to work on this please!
Author
Owner

@github-actions[bot] commented on GitHub (Sep 30, 2025):

Great! I assigned you (@Zacgoose) to the issue. Have fun working on it!

<!-- gh-comment-id:3354126029 --> @github-actions[bot] commented on GitHub (Sep 30, 2025): Great! I assigned you (@Zacgoose) to the issue. Have fun working on it!
Author
Owner

@Zacgoose commented on GitHub (Oct 4, 2025):

This does not seem to be a problem in latest dev

<!-- gh-comment-id:3367790262 --> @Zacgoose commented on GitHub (Oct 4, 2025): This does not seem to be a problem in latest dev
Author
Owner

@PeterVive commented on GitHub (Oct 4, 2025):

It does for me still.

Editing the tenant group and adding a tenant that way works. Editing the tenant and adding it to a tenant group that way doesn’t, and they use different identifiers in the underlying table defaultDomainName vs tenantId.

<!-- gh-comment-id:3367862516 --> @PeterVive commented on GitHub (Oct 4, 2025): It does for me still. Editing the tenant group and adding a tenant that way works. Editing the tenant and adding it to a tenant group that way doesn’t, and they use different identifiers in the underlying table defaultDomainName vs tenantId.
Author
Owner

@JohnDuprey commented on GitHub (Oct 5, 2025):

Fixeds in dev

<!-- gh-comment-id:3369171611 --> @JohnDuprey commented on GitHub (Oct 5, 2025): Fixeds in dev
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/CIPP#2201
No description provided.