mirror of
https://github.com/KelvinTegelaar/CIPP.git
synced 2026-04-25 16:26:09 +03:00
[GH-ISSUE #894] BUG: Adding mailbox permissions without automapping #455
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#455
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 @Github-campai on GitHub (Apr 20, 2022).
Original GitHub issue: https://github.com/KelvinTegelaar/CIPP/issues/894
Describe the bug
When adding mailbox permissions without automapping the error: "Object reference not set to an instance of an object." is given. This happens in all tenants, SAM Permissions OK, Tenant checks 2 green, Cleared cache.
To Reproduce
Expected behavior
A new permission entry without automapping to be added to the mailbox permissions, we have used it previously on older builds with no issues.
Screenshots

It still works fine if we use the standard, with automapping permissions.
Desktop (please complete the following information):
Additional context
Frontend 2.5.0
Backend 1.10.0
@KelvinTegelaar commented on GitHub (Apr 21, 2022):
Fixed in dev.