[GH-ISSUE #5457] [Bug]: GDAP Check still listing 12 GDAP groups #2631

Closed
opened 2026-03-02 13:53:53 +03:00 by kerem · 9 comments
Owner

Originally created by @joelmacklow on GitHub (Feb 24, 2026).
Original GitHub issue: https://github.com/KelvinTegelaar/CIPP/issues/5457

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

In v10.1.1 the number of recommended GDAP role memberships seems to have increased from 12 to 15 as per https://docs.cipp.app/setup/installation/recommended-roles. The GDAP Check pane seems to imply that there are still only 12. Is it checking for 15 or still 12?

Steps

  1. CIPP
  2. Application Settings
  3. Permissions
  4. GDAP Check pane lists "User is a member of the 12 CIPP Recommended GDAP groups"

Environment Type

Non-sponsored user

Front End Version

v10.1.1

Back End Version

v10.1.1

Relevant Logs / Stack Trace


Originally created by @joelmacklow on GitHub (Feb 24, 2026). Original GitHub issue: https://github.com/KelvinTegelaar/CIPP/issues/5457 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 In v10.1.1 the number of recommended GDAP role memberships seems to have increased from 12 to 15 as per https://docs.cipp.app/setup/installation/recommended-roles. The GDAP Check pane seems to imply that there are still only 12. Is it checking for 15 or still 12? Steps 1. CIPP 2. Application Settings 3. Permissions 4. GDAP Check pane lists "User is a member of the 12 CIPP Recommended GDAP groups" ### Environment Type Non-sponsored user ### Front End Version v10.1.1 ### Back End Version v10.1.1 ### Relevant Logs / Stack Trace ```plaintext ```
Author
Owner

@github-actions[bot] commented on GitHub (Feb 24, 2026):

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:3955230354 --> @github-actions[bot] commented on GitHub (Feb 24, 2026): 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

@joelmacklow commented on GitHub (Feb 24, 2026):

Sidepoint: It is my understanding (I could be wrong here) that if the number of roles in a GDAP Role Template are changed then a new invitation for the tenant will need to be created and approved in all existing tenants that use that template and the previous existing GDAP relationship terminated.

Documentation suggestion: Perhaps the docs for https://docs.cipp.app/setup/installation/recommended-roles should clarify the above?

<!-- gh-comment-id:3955249230 --> @joelmacklow commented on GitHub (Feb 24, 2026): Sidepoint: It is my understanding (I could be wrong here) that if the number of roles in a GDAP Role Template are changed then a new invitation for the tenant will need to be created and approved in all existing tenants that use that template and the previous existing GDAP relationship terminated. Documentation suggestion: Perhaps the docs for https://docs.cipp.app/setup/installation/recommended-roles should clarify the above?
Author
Owner

@CW-ZacR commented on GitHub (Feb 25, 2026):

I would like to work on this please!

<!-- gh-comment-id:3956801199 --> @CW-ZacR commented on GitHub (Feb 25, 2026): I would like to work on this please!
Author
Owner

@github-actions[bot] commented on GitHub (Feb 25, 2026):

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

<!-- gh-comment-id:3956802074 --> @github-actions[bot] commented on GitHub (Feb 25, 2026): Great! I assigned you (@CW-ZacR) to the issue. Have fun working on it!
Author
Owner

@CW-ZacR commented on GitHub (Feb 25, 2026):

Sidepoint: It is my understanding (I could be wrong here) that if the number of roles in a GDAP Role Template are changed then a new invitation for the tenant will need to be created and approved in all existing tenants that use that template and the previous existing GDAP relationship terminated.

Documentation suggestion: Perhaps the docs for https://docs.cipp.app/setup/installation/recommended-roles should clarify the above?

if the relationship contains the required roles (including new ones) then it'll be updated with your new GDAP permissions mapping. If the relationship does not contain the new roles you will need to do a new GDAP invite for those customers who have not got it. no easy way around it. Yes, it would also be best to remove the old ones as well once you have the new one established.

<!-- gh-comment-id:3956812396 --> @CW-ZacR commented on GitHub (Feb 25, 2026): > Sidepoint: It is my understanding (I could be wrong here) that if the number of roles in a GDAP Role Template are changed then a new invitation for the tenant will need to be created and approved in all existing tenants that use that template and the previous existing GDAP relationship terminated. > > Documentation suggestion: Perhaps the docs for https://docs.cipp.app/setup/installation/recommended-roles should clarify the above? if the relationship contains the required roles (including new ones) then it'll be updated with your new GDAP permissions mapping. If the relationship does not contain the new roles you will need to do a new GDAP invite for those customers who have not got it. no easy way around it. Yes, it would also be best to remove the old ones as well once you have the new one established.
Author
Owner

@Zacgoose commented on GitHub (Feb 25, 2026):

wrong account, should be this one haha

<!-- gh-comment-id:3956869226 --> @Zacgoose commented on GitHub (Feb 25, 2026): wrong account, should be this one haha
Author
Owner

@Zacgoose commented on GitHub (Feb 25, 2026):

I would like to work on this please!

<!-- gh-comment-id:3956869521 --> @Zacgoose commented on GitHub (Feb 25, 2026): I would like to work on this please!
Author
Owner

@github-actions[bot] commented on GitHub (Feb 25, 2026):

Sorry, can't help you here. This issue already has a volunteer.

<!-- gh-comment-id:3956869837 --> @github-actions[bot] commented on GitHub (Feb 25, 2026): Sorry, can't help you here. This issue already has a volunteer.
Author
Owner

@KelvinTegelaar commented on GitHub (Feb 25, 2026):

Fixed in dev

<!-- gh-comment-id:3959084873 --> @KelvinTegelaar commented on GitHub (Feb 25, 2026): Fixed 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#2631
No description provided.