Missing or insecure "Content-Security-Policy" header (API) #5757
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
✔️ Deploy Preview for chef-automate ready! 🔨 Explore the source changes: 83f5676 🔍 Inspect the deploy log: https://app.netlify.com/sites/chef-automate/deploys/618c118ac81a7d0007a5d11f 😎 Browse the preview: https://deploy-preview-5757--chef-automate.netlify.app |
Venkatesh-rengasamy
added
security
automate-ui
Team: Kinetic
|
Kudos, SonarCloud Quality Gate passed!
|
kalroy
force-pushed
the
venkatesh/content_sec_policy
branch
from
8a95162
to
789f293
Compare
kagarmoe
changed the title
|
I added |
dishanktiwari2501
approved these changes
Nov 10, 2021
Signed-off-by: Venkatesh-rengasamy <vrengasa@progress.com>
Signed-off-by: Venkatesh-rengasamy <vrengasa@progress.com>
Signed-off-by: Kallol Roy <karoy@progress.com>
kalroy
force-pushed
the
venkatesh/content_sec_policy
branch
from
789f293
to
83f5676
Compare
|
Kudos, SonarCloud Quality Gate passed!
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Signed-off-by: Venkatesh-rengasamy vrengasa@progress.com
🔩 Description: What code changed, and why?
Add Content-Security-Policy header to resolve blank screen after SAML signin.
⛓️ Related Resources
#4856
👍 Definition of Done
👟 How to Build and Test the Change
Login into SAML account and see you are getting home page insteadof blank screen.
✅ Checklist
All PRs must tick these:
With occasional exceptions, all PRs from Progress employees must tick these:
make spellin any component directory)All PRs from Progress employees should tick these if appropriate:
Please add a note next to any checkbox above if you are NOT ticking it.
📷 Screenshots, if applicable