starred/CIPP

Fork 0

mirror of https://github.com/KelvinTegelaar/CIPP.git synced 2026-04-26 00:36:27 +03:00

[GH-ISSUE #1319] Alerts not detecting items at risk of expiring #730

New issue

Closed

opened 2026-03-02 12:44:42 +03:00 by kerem · 7 comments

kerem commented

2026-03-02 12:44:42 +03:00

Owner

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

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

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 20, 2023). Original GitHub issue: https://github.com/KelvinTegelaar/CIPP/issues/1319 ### 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 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:42 +03:00

closed this issue
added the
bug

no-activity

unconfirmed-by-user
labels

kerem commented

2026-03-02 12:44:44 +03:00

Author

Owner

@github-actions[bot] commented on GitHub (Jan 20, 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!".

@github-actions[bot] commented on GitHub (Jan 20, 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!".

kerem commented

2026-03-02 12:44:44 +03:00

Author

Owner

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

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

@MBstatsara commented on GitHub (Jan 20, 2023): I confirm that I have checked the documentation thoroughly and believe this to be an actual bug.

kerem commented

2026-03-02 12:44:44 +03:00

Author

Owner

@KelvinTegelaar commented on GitHub (Jan 20, 2023):

Stop reopening this each day. You're not a sponsor, so don't game the system. :)

@KelvinTegelaar commented on GitHub (Jan 20, 2023): Stop reopening this each day. You're not a sponsor, so don't game the system. :)

kerem commented

2026-03-02 12:44:44 +03:00

Author

Owner

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

Sorry, wasnt meant to be gaming the system, its reporting as closing as not confirmed by the user, even though i am doing so!
How do we get support for this in a better way? How do i go about getting paid support?
Thanks

@MBstatsara commented on GitHub (Jan 20, 2023): Sorry, wasnt meant to be gaming the system, its reporting as closing as not confirmed by the user, even though i am doing so! How do we get support for this in a better way? How do i go about getting paid support? Thanks

kerem commented

2026-03-02 12:44:44 +03:00

Author

Owner

@KelvinTegelaar commented on GitHub (Jan 20, 2023):

Bugs can be reported by anyone, but are only picked up if a contributor has the time, Sponsors can prioritize their bugs to get higher in the queue.

to become a sponsor, check this url: https://github.com/sponsors/KelvinTegelaar/sponsorships?sponsor=KelvinTegelaar&tier_id=101398&preview=false

Regards,

@KelvinTegelaar commented on GitHub (Jan 20, 2023): Bugs can be reported by anyone, but are only picked up if a contributor has the time, Sponsors can prioritize their bugs to get higher in the queue. to become a sponsor, check this url: https://github.com/sponsors/KelvinTegelaar/sponsorships?sponsor=KelvinTegelaar&tier_id=101398&preview=false Regards,

kerem commented

2026-03-02 12:44:44 +03:00

Author

Owner

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

This issue is stale because it has been open 10 days with no activity. We will close this issue soon. If you want this feature implemented you can contribute it. See: https://cipp.app/GettingStarted/Contributions/ . Please notify the team if you are working on this yourself.

@github-actions[bot] commented on GitHub (Jan 30, 2023): This issue is stale because it has been open 10 days with no activity. We will close this issue soon. If you want this feature implemented you can contribute it. See: https://cipp.app/GettingStarted/Contributions/ . Please notify the team if you are working on this yourself.

kerem commented

2026-03-02 12:44:44 +03:00

Author

Owner

@github-actions[bot] commented on GitHub (Feb 13, 2023):

This issue was closed because it has been stalled for 14 days with no activity.

@github-actions[bot] commented on GitHub (Feb 13, 2023): This issue was closed because it has been stalled for 14 days with no activity.

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#730

No description provided.

Rows
Columns