feat(Apps): make default configuration secure #871
Merged
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
nicoprow
force-pushed
the
feat/secure-defaults
branch
from
4d619cf to
05e0a1a
Compare
…re with authorized APIs
nicoprow
force-pushed
the
feat/secure-defaults
branch
from
05e0a1a to
3424b7c
Compare
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
This pull request changes the default configuration for BPDM applications to have authenticated API and connect with other BPDM services in an authenticated way. This increases security as one has to actively opt-out of security by switching off security of the app and the connection to its clients.
Pre-review checks
Please ensure to do as many of the following checks as possible, before asking for committer review: