mirror of
https://github.com/KelvinTegelaar/CIPP.git
synced 2026-04-25 08:16:01 +03:00
[GH-ISSUE #813] BUG: 500 errors during offboarding process - No 'Access-Control-Allow-Origin' header is present on the requested resource. #409
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#409
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 @SuburbanTotoro on GitHub (Mar 8, 2022).
Original GitHub issue: https://github.com/KelvinTegelaar/CIPP/issues/813
Describe the bug
During Step 4 of the offboarding process, "request failed with status code 500" appears and all steps appear to fail. No actions appear to occur, and manual offboarding is required.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
The expected behavior is that the offboarding wizard completes the offboarding task.
Screenshots

Desktop (please complete the following information):
Additional context
The console is returning this error:
@KelvinTegelaar commented on GitHub (Mar 8, 2022):
CORS is never an issue, and you can ignore that.
Your issue most likely is related to the access token, most tasks there use the Exchange token. Perform an accces check for that tenant to see if its working.
Small note; currently half of the internet is offline due to server disruptions, might also be related to that if this is the only error.
@SuburbanTotoro commented on GitHub (Mar 9, 2022):
Thank you very much Kevin, running the tenant access check shows an error I know how to deal with:
Failed to connect to Exchange: AADSTS50078: Presented multi-factor authentication has expired due to policies configured by your administrator, you must refresh your multi-factor authentication to access '00000002-0000-0ff1-ce00-000000000000'. Trace ID: a3e7f991-dfdf-4b80-bb05-53dfd3eac200 Correlation ID: efe767bb-c6a9-4eeb-8109-e9a4bbb9a37d Timestamp: 2022-03-09 16:58:02Z
I hope you have a great day and really appreciate such a quick response to this,
Benjamin Sanchez
Senior Automation Engineer
T:
971-288-0880tel:9712880880
E:
@.@.>
W:
https://genuinetechnology.comhttps://genuinetechnology.com/
[Genuine Technology Logo]https://genuinetechnology.com/
Please help us serve you! Send all requests through the 24/7 support team:
Email: @.*** @.***>
Phone: 9tel:971888891171-888-8911tel:9718888911
https://mygenuine.tech/Requests made directly to individual staff may have a significantly delayed response and do not have SLA guarantees
From: KelvinTegelaar @.>
Sent: Tuesday, March 8, 2022 10:49 AM
To: KelvinTegelaar/CIPP @.>
Cc: Benjamin Sanchez @.>; Author @.>
Subject: Re: [KelvinTegelaar/CIPP] BUG: 500 errors during offboarding process - No 'Access-Control-Allow-Origin' header is present on the requested resource. (Issue #813)
CORS is never an issue, and you can ignore that.
Your issue most likely is related to the access token, most tasks there use the Exchange token. Perform an accces check for that tenant to see if its working.
Small note; currently half of the internet is offline due to server disruptions, might also be related to that if this is the only error.
—
Reply to this email directly, view it on GitHubhttps://github.com/KelvinTegelaar/CIPP/issues/813#issuecomment-1062094249, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AW5S5BW2TLYLYU3HZATMTYTU66OJZANCNFSM5QHF2NBA.
Triage notifications on the go with GitHub Mobile for iOShttps://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Androidhttps://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.
You are receiving this because you authored the thread.Message ID: @.@.>>
@KelvinTegelaar commented on GitHub (Mar 11, 2022):
So fixed :) Will try to have somewhat clearer error messages in a future version too to show its an access token issue.