Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Addition of "Enforcement Mode" for Cross Domain Request Enforcement in URL properties #958

Closed
curtkersey opened this issue Apr 8, 2024 · 1 comment · Fixed by #974
Closed
Labels
Backlog issue will be tracked by JIRA in backlog enhancement
Milestone

Comments

@curtkersey
Copy link

Environment
TMOS/Bigip Version: 16.1.4
Terraform Version: 1.7.0
Terraform BIG-IP provider Version: 1.22.0

Is your feature request related to a problem? Please describe.

I am helping a customer with their Terraform deployments for ASM policies. Currently when deploying WAF policies on the BIG-IP and adding a URL entity, they choose the "Enforcement Mode" of "Disabled" for the Cross Domain Request Enforcement. Now deploying via Terraform, they need to replicate current policy deployments, which is to specify "Disabled". Currently the provider defaults to "Enforce on ASM". I am attaching a document to show screen shots of BIG-IP.

CORSheaders.pdf

Describe the solution you'd like

We would like to have this added to the Terraform provider and include the current options for Cross Domain Request Enforcement, which include: Disabled, Remove all CORS headers, Replace CORS headers, or Enforce on ASM.

@pgouband
Copy link
Collaborator

Hi,

Thanks for reporting. Added to the backlog and internal tracking ID for this request is: INFRAANO-1538.

@pgouband pgouband added the Backlog issue will be tracked by JIRA in backlog label Apr 12, 2024
@RavinderReddyF5 RavinderReddyF5 added this to the v1.22.1 milestone May 9, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Backlog issue will be tracked by JIRA in backlog enhancement
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants