mirror of
https://github.com/KelvinTegelaar/CIPP.git
synced 2026-04-25 16:26:09 +03:00
[GH-ISSUE #1278] OneDrive not showing names #713
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#713
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 @Exigo-CIPP on GitHub (Dec 21, 2022).
Original GitHub issue: https://github.com/KelvinTegelaar/CIPP/issues/1278
Description
Within our hosted CIPP session. I have noticed OneDrive is showing what I assume is the hex data of the user rather than the username.
Permissions Check all successful.
Your refresh token matches key vault.
Your access token contains the MFA claim.
Your Secure Application Model has all required permissions
When checking tenant access permission, it showed connect and connected to exchange. It's the same with all our clients except one. When I run the access check, still successful.
Environment data
@github-actions[bot] commented on GitHub (Dec 21, 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!".
@KelvinTegelaar commented on GitHub (Dec 21, 2022):
Not a bug, please check the documentation.