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

[DOC] Update dynamic CSP rule configuration to only allow frame-ancestors #7024

Closed
1 of 4 tasks
tianleh opened this issue Apr 24, 2024 · 1 comment · Fixed by #7026
Closed
1 of 4 tasks

[DOC] Update dynamic CSP rule configuration to only allow frame-ancestors #7024

tianleh opened this issue Apr 24, 2024 · 1 comment · Fixed by #7026
Assignees
Labels
3 - Done Issue is done/complete v2.14.0
Milestone

Comments

@tianleh
Copy link
Member

tianleh commented Apr 24, 2024

What do you want to do?

  • Request a change to existing documentation
  • Add new documentation
  • Report a technical problem with the documentation
  • Other

Tell us about your request. Provide a summary of the request and all versions that are affected.
This is about an existing document. https://github.com/opensearch-project/documentation-website/blob/main/_dashboards/csp/csp-dynamic-configuration.md

In the existing doc for 2.13.0, we allowed customers to configure the whole CSP rule. To avoid customers accidentally change such, we have made a change to limit customers to configure only one directive frame-ancestors of the CSP rule. This change will go to 2.14.0 as well as future patch releases for 2.13.

What other resources are available? Provide links to related issues, POCs, steps for testing, etc.

The README.md file has been updated to reflect the current situation.
https://github.com/opensearch-project/OpenSearch-Dashboards/blob/main/src/plugins/csp_handler/README.md

@tianleh
Copy link
Member Author

tianleh commented Apr 24, 2024

I am creating a PR for such.

@hdhalter hdhalter added this to the v2.14 milestone Apr 24, 2024
@hdhalter hdhalter added the 1 - Backlog - DEV Developer assigned to issue is responsible for creating PR. label Apr 24, 2024
@hdhalter hdhalter added 2 - In progress Issue/PR: The issue or PR is in progress. and removed 1 - Backlog - DEV Developer assigned to issue is responsible for creating PR. labels Apr 25, 2024
@hdhalter hdhalter added 3 - Done Issue is done/complete and removed 2 - In progress Issue/PR: The issue or PR is in progress. labels May 1, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
3 - Done Issue is done/complete v2.14.0
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants