fix(deployment): keycloak blocked due to security violation in ocis_keycloak example #9025
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
|
Thanks for opening this pull request! The maintainers of this repository would appreciate it if you would create a changelog item based on your changes. |
saw-jan
changed the title
|
micbar
approved these changes
Apr 30, 2024
DeepDiver1975
approved these changes
Apr 30, 2024
ownclouders
pushed a commit
that referenced
this pull request
Apr 30, 2024
7 tasks
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.
Description
ocis_keycloak deployment example doesn't work with current latest ocis because the PR #8777 has hardened some security.
This PR fixes the problem by adding custom
csp.yamlfile in the deployment exampleRelated Issue
Motivation and Context
How Has This Been Tested?
Types of changes
Checklist: