starred/CIPP

Fork 0

mirror of https://github.com/KelvinTegelaar/CIPP.git synced 2026-04-25 16:26:09 +03:00

[GH-ISSUE #5277] [Bug]: Disable Security Defaults is applied after policy deployment #2536

New issue

Closed

opened 2026-03-02 13:53:09 +03:00 by kerem · 4 comments

kerem commented

2026-03-02 13:53:09 +03:00

Owner

Originally created by @sfaxluke on GitHub (Jan 28, 2026).
Original GitHub issue: https://github.com/KelvinTegelaar/CIPP/issues/5277

Originally assigned to: @kris6673 on GitHub.

Required confirmations before submitting

I can reproduce this issue on the latest released versions of both CIPP and CIPP-API.
I have searched existing issues (both open and closed) to avoid duplicates.
I am not requesting general support; this is an actual bug report.

Issue Description

When deploying a CA policy and selecting "Disable Security defaults if enabled when creating policy", it errors on the deployment of the policy due to security defaults being enabled.

It feels like because these actions are performed back to back there is not enough of a delay for the policy creation to succeed.

To note that if I give it 5m (or there abouts) and click the redeploy policy button again it works without fault, so it has processed the disable security defaults. I don't know if it's worth having a check if SD is a disabled job that runs every 10s for a minute or so, and once it succeeds, then it issues the CA policy deployment. Maybe trigger the delay mechanism if SD is detected as enabled, otherwise if it is disabled, then send the policy change straight to graph?

Environment Type

Front End Version

10.0.0.3

Back End Version

10.0.0.5

Relevant Logs / Stack Trace

Originally created by @sfaxluke on GitHub (Jan 28, 2026). Original GitHub issue: https://github.com/KelvinTegelaar/CIPP/issues/5277 Originally assigned to: @kris6673 on GitHub. ### Required confirmations before submitting - [x] **I can reproduce this issue on the latest released versions** of both CIPP and CIPP-API. - [x] **I have searched existing issues** (both open and closed) to avoid duplicates. - [x] I am **not** requesting general support; this is an actual bug report. ### Issue Description When deploying a CA policy and selecting "Disable Security defaults if enabled when creating policy", it errors on the deployment of the policy due to security defaults being enabled. It feels like because these actions are performed back to back there is not enough of a delay for the policy creation to succeed. <img width="598" height="949" alt="Image" src="https://github.com/user-attachments/assets/bf86a9df-ae9f-4111-9338-ecb5245ff7c4" /> To note that if I give it 5m (or there abouts) and click the redeploy policy button again it works without fault, so it has processed the disable security defaults. I don't know if it's worth having a check if SD is a disabled job that runs every 10s for a minute or so, and once it succeeds, then it issues the CA policy deployment. Maybe trigger the delay mechanism if SD is detected as enabled, otherwise if it is disabled, then send the policy change straight to graph? ### Environment Type Sponsored (paying) user ### Front End Version 10.0.0.3 ### Back End Version 10.0.0.5 ### Relevant Logs / Stack Trace ```plaintext ```

kerem

2026-03-02 13:53:09 +03:00

closed this issue
added the
bug

unconfirmed-by-user

not-assigned
labels

kerem commented

2026-03-02 13:53:10 +03:00

Author

Owner

@github-actions[bot] commented on GitHub (Jan 28, 2026):

Thank you for reporting a potential bug. If you would like to work on this bug, please comment:

I would like to work on this please!

Thank you for helping us maintain the project!

@github-actions[bot] commented on GitHub (Jan 28, 2026): Thank you for reporting a potential bug. If you would like to work on this bug, please comment: > I would like to work on this please! Thank you for helping us maintain the project!

kerem commented

2026-03-02 13:53:10 +03:00

Author

Owner

@kris6673 commented on GitHub (Feb 14, 2026):

I would like to work on this please!

@kris6673 commented on GitHub (Feb 14, 2026): I would like to work on this please!

kerem commented

2026-03-02 13:53:10 +03:00

Author

Owner

@github-actions[bot] commented on GitHub (Feb 14, 2026):

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

@github-actions[bot] commented on GitHub (Feb 14, 2026): Great! I assigned you (@kris6673) to the issue. Have fun working on it!

kerem commented

2026-03-02 13:53:10 +03:00

Author

Owner

@KelvinTegelaar commented on GitHub (Feb 16, 2026):

Improved in CA deployment

@KelvinTegelaar commented on GitHub (Feb 16, 2026): Improved in CA deployment

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

No description provided.

Rows
Columns