[GH-ISSUE #1501] Invalid SSPR status in BPA Report #820

Closed
opened 2026-03-02 12:45:31 +03:00 by kerem · 3 comments
Owner

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.

image

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

Non-Sponsored
Frontend: 3.4.0
Backend: 1.9.0
Cache: Cleared
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. ![image](https://user-images.githubusercontent.com/98537980/233646563-6630713c-80ed-41fe-8dc9-acb597ecea2b.png) 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 ```PowerShell Non-Sponsored Frontend: 3.4.0 Backend: 1.9.0 Cache: Cleared ```
kerem 2026-03-02 12:45:31 +03:00
Author
Owner

@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!".

<!-- gh-comment-id:1517839860 --> @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!".
Author
Owner

@pricenfi commented on GitHub (Apr 21, 2023):

I confirm that I have checked the documentation thoroughly and believe this to be an actual bug.

<!-- gh-comment-id:1517841284 --> @pricenfi commented on GitHub (Apr 21, 2023): I confirm that I have checked the documentation thoroughly and believe this to be an actual bug.
Author
Owner

@KelvinTegelaar commented on GitHub (Apr 21, 2023):

Yup, that's a bug. Fixed in dev.

<!-- gh-comment-id:1517842953 --> @KelvinTegelaar commented on GitHub (Apr 21, 2023): Yup, that's a bug. Fixed in dev.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/CIPP#820
No description provided.