[GH-ISSUE #1314] Alerts not reporting certificate/token expiry #726

Closed
opened 2026-03-02 12:44:41 +03:00 by kerem · 6 comments
Owner

Originally created by @MBstatsara on GitHub (Jan 19, 2023).
Original GitHub issue: https://github.com/KelvinTegelaar/CIPP/issues/1314

Originally assigned to: @MBstatsara on GitHub.

Description

Hi there
It seems as though at some tenants we have tokens expiring for apple, and 3rd party apps which are not being detected.
We have an azure automation setup on one client but no way to manually run a report across all tenants.
As we have this issue we have since had to check other tenants and found other apps expiring which arent being alerted on.

There is no graph report to check these manually, so i cant verify how wide spread this is.
I specifically found a tenant with a certificate token expiring and run the alerts wizard to check this and report on expiring tokens, but it does not.

anyway i can manually check all of them from CIPP without connecting to each tenant directly?
While we try and fix the alerting.

PS would also be handy to be alerted on if any errors occur in the attempts to connect to tenants etc

No issues with anything else, just alerting i think!

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

Environment data

Environment data
Version Frontend
Latest: 2.19.1
Current: 2.19.1
Version Backend
Latest: 2.8.0
Current: 2.8.0
Originally created by @MBstatsara on GitHub (Jan 19, 2023). Original GitHub issue: https://github.com/KelvinTegelaar/CIPP/issues/1314 Originally assigned to: @MBstatsara on GitHub. ### Description Hi there It seems as though at some tenants we have tokens expiring for apple, and 3rd party apps which are not being detected. We have an azure automation setup on one client but no way to manually run a report across all tenants. As we have this issue we have since had to check other tenants and found other apps expiring which arent being alerted on. There is no graph report to check these manually, so i cant verify how wide spread this is. I specifically found a tenant with a certificate token expiring and run the alerts wizard to check this and report on expiring tokens, but it does not. anyway i can manually check all of them from CIPP without connecting to each tenant directly? While we try and fix the alerting. PS would also be handy to be alerted on if any errors occur in the attempts to connect to tenants etc No issues with anything else, just alerting i think! "I confirm that I have checked the documentation thoroughly and believe this to be an actual bug.". ### Environment data ```PowerShell Environment data Version Frontend Latest: 2.19.1 Current: 2.19.1 Version Backend Latest: 2.8.0 Current: 2.8.0 ```
kerem 2026-03-02 12:44:41 +03:00
Author
Owner

@github-actions[bot] commented on GitHub (Jan 19, 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:1397138265 --> @github-actions[bot] commented on GitHub (Jan 19, 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

@MBstatsara commented on GitHub (Jan 19, 2023):

I can confirm this bug still exists.
I have gone through clearing out all tenants cache and all tenants, removing all alerts and selecting the one tenant i know still has the cert.
After wiping everything and renabling on all tenants, i have had one alert with 25 tenants who have apple certs and applications expiring in the next 30days, i have then only had one further alert for the applications still expiring but nothing else, i have checked and we have not replaced the certs yet.
Definitely a bug in the system somewhere!
Its not running the check any more...

<!-- gh-comment-id:1397138416 --> @MBstatsara commented on GitHub (Jan 19, 2023): I can confirm this bug still exists. I have gone through clearing out all tenants cache and all tenants, removing all alerts and selecting the one tenant i know still has the cert. After wiping everything and renabling on all tenants, i have had one alert with 25 tenants who have apple certs and applications expiring in the next 30days, i have then only had one further alert for the applications still expiring but nothing else, i have checked and we have not replaced the certs yet. Definitely a bug in the system somewhere! Its not running the check any more...
Author
Owner

@MBstatsara commented on GitHub (Jan 19, 2023):

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

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

@github-actions[bot] commented on GitHub (Jan 19, 2023):

Great! I assigned you (@MBstatsara) to the issue. Have fun working on it!

<!-- gh-comment-id:1397140893 --> @github-actions[bot] commented on GitHub (Jan 19, 2023): Great! I assigned you (@MBstatsara) to the issue. Have fun working on it!
Author
Owner

@github-actions[bot] commented on GitHub (Jan 19, 2023):

Sorry, can't help you here. This issue already has a volunteer.

<!-- gh-comment-id:1397144145 --> @github-actions[bot] commented on GitHub (Jan 19, 2023): Sorry, can't help you here. This issue already has a volunteer.
Author
Owner

@MBstatsara commented on GitHub (Jan 19, 2023):

@KelvinTegelaar
Is there anyway we can get this looked at? happy to help troubleshoot etc.
No idea really where to start, but i have multiple tenants, with items only found on an initial scan and then never again.

<!-- gh-comment-id:1397145482 --> @MBstatsara commented on GitHub (Jan 19, 2023): @KelvinTegelaar Is there anyway we can get this looked at? happy to help troubleshoot etc. No idea really where to start, but i have multiple tenants, with items only found on an initial scan and then never again.
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#726
No description provided.