[GH-ISSUE #3274] JIT admins not being deleted after end time #1536

Closed
opened 2026-03-02 13:45:01 +03:00 by kerem · 8 comments
Owner

Originally created by @rajeevan23 on GitHub (Jan 15, 2025).
Original GitHub issue: https://github.com/KelvinTegelaar/CIPP/issues/3274

Originally assigned to: @kris6673 on GitHub.

Description

Hello

We have noticed that JIT admins are not being deleted after the end time. The scheduler shows the status as "Completed" but displays the following error message:

image

Thanks,
Raj

Environment data

Non-sponsored instance 
Front end version number: 7.0.2
Back end version number: 7.0.2
Tried Tenant Cache Clear: flase
Tried Token Cache Clear: false
Originally created by @rajeevan23 on GitHub (Jan 15, 2025). Original GitHub issue: https://github.com/KelvinTegelaar/CIPP/issues/3274 Originally assigned to: @kris6673 on GitHub. ### Description Hello We have noticed that JIT admins are not being deleted after the end time. The scheduler shows the status as "Completed" but displays the following error message: ![image](https://github.com/user-attachments/assets/976e98cd-8c6c-4417-bf8c-7d3cf429e59b) Thanks, Raj ### Environment data ```PowerShell Non-sponsored instance Front end version number: 7.0.2 Back end version number: 7.0.2 Tried Tenant Cache Clear: flase Tried Token Cache Clear: false ```
kerem 2026-03-02 13:45:01 +03:00
Author
Owner

@github-actions[bot] commented on GitHub (Jan 15, 2025):

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://docs.cipp.app/
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:2592808686 --> @github-actions[bot] commented on GitHub (Jan 15, 2025): 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://docs.cipp.app/ 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

@rajeevan23 commented on GitHub (Jan 15, 2025):

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

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

@mruiterHU commented on GitHub (Jan 15, 2025):

I second this

<!-- gh-comment-id:2592838135 --> @mruiterHU commented on GitHub (Jan 15, 2025): I second this
Author
Owner

@kris6673 commented on GitHub (Jan 15, 2025):

I would like to work on this please!

<!-- gh-comment-id:2593876905 --> @kris6673 commented on GitHub (Jan 15, 2025): I would like to work on this please!
Author
Owner

@github-actions[bot] commented on GitHub (Jan 15, 2025):

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

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

@kris6673 commented on GitHub (Jan 15, 2025):

Thanks the making the issue @rajeevan23! Has been fixed in dev and will be en next hotfix/release.
You will need to do the Expiration Action manually, for the JIT admins created until the fix is released.

<!-- gh-comment-id:2593928659 --> @kris6673 commented on GitHub (Jan 15, 2025): Thanks the making the issue @rajeevan23! Has been fixed in dev and will be en next hotfix/release. You will need to do the Expiration Action manually, for the JIT admins created until the fix is released.
Author
Owner

@rajeevan23 commented on GitHub (Jan 15, 2025):

Thank you @kris6673 !

<!-- gh-comment-id:2593938629 --> @rajeevan23 commented on GitHub (Jan 15, 2025): Thank you @kris6673 !
Author
Owner

@kris6673 commented on GitHub (Jan 17, 2025):

Added in dev and is in yesterdays hotfix. You can close this as completed @rajeevan23 :)

<!-- gh-comment-id:2598703431 --> @kris6673 commented on GitHub (Jan 17, 2025): Added in dev and is in yesterdays hotfix. You can close this as completed @rajeevan23 :)
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#1536
No description provided.