mirror of
https://github.com/KelvinTegelaar/CIPP.git
synced 2026-04-25 08:16:01 +03:00
[GH-ISSUE #1501] Invalid SSPR status in BPA Report #820
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#820
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 @pricenfi on GitHub (Apr 21, 2023).
Original GitHub issue: https://github.com/KelvinTegelaar/CIPP/issues/1501
Description
The current logic used for determining if self-service password reset is enabled for a tenant can result in a false positive state.
The BPA report shows this tenant has having SSPR enabled, however manually checking the status the setting is disabled. Running the graph query from the code generates the following results.
Adding a simple check if the $CapableState state is equal to 0 prior to reporting SSPR is enabled should avoid the false positive.
Environment data
@github-actions[bot] commented on GitHub (Apr 21, 2023):
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!".
@pricenfi commented on GitHub (Apr 21, 2023):
I confirm that I have checked the documentation thoroughly and believe this to be an actual bug.
@KelvinTegelaar commented on GitHub (Apr 21, 2023):
Yup, that's a bug. Fixed in dev.