mirror of
https://github.com/KelvinTegelaar/CIPP.git
synced 2026-04-25 16:26:09 +03:00
[GH-ISSUE #1177] Post GDAP Authentication Issues #641
Labels
No labels
API
Feature
NotABug
NotABug
Planned
Sponsor Priority
Sponsor Priority
bug
documentation
duplicate
enhancement
needs more info
no-activity
no-priority
not-assigned
pull-request
react-conversion
react-conversion
roadmap
security
stale
unconfirmed-by-user
unconfirmed-by-user
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/CIPP#641
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @Danpoulter97 on GitHub (Oct 31, 2022).
Original GitHub issue: https://github.com/KelvinTegelaar/CIPP/issues/1177
Description
I know that there is limited or no support in relation to the GDAP Migration tool but, I can perform the migration fine but once the DAP permissions are removed, I can no longer access the tenant. I get the error 'The user you have used for your Secure Application Model is a guest in this tenant, or your are using GDAP and have not added the user to the correct group. Please delete the guest user to gain access to this tenant.' (There is not a guest user associated with this)
I have added the CIPP-SAM user and my own user to the below groups/roles:
GDAP 365 - Application Administrator
GDAP 365 -User Administrator
GDAP 365 -Intune Administrator
GDAP 365 -Exchange Administrator
GDAP 365 -Security Administrator
GDAP 365 -Cloud App Security Administrator
Am I missing a critical group?
I am running the latest version of CIPP and CIPP-API.
Environment data
Edit: I have followed the steps here https://cipp.app/docs/user/usingcipp/GDAP/migration/#recommended-roles-for-cipp
@github-actions[bot] commented on GitHub (Oct 31, 2022):
Thank you for creating a bug. Please make sure your bug is indeed a unique case by checking current and past issues, and reading the complete documentation at https://kelvintegelaar.github.io/CIPP
If your bug is a known documentation issue, it will be closed without notice by a contributor. To confirm that this is not a bug found in the documentation, please copy and paste the following comment: "I confirm that I have checked the documentation thoroughly and believe this to be an actual bug.".
Without confirming, your report will be closed in 24 hours. If you'd like this bug to be assigned to you, please comment "I would like to work on this please!".
@icisupport commented on GitHub (Oct 31, 2022):
We're having this issue as well.
@KelvinTegelaar commented on GitHub (Oct 31, 2022):