Use existing tls and authentication configuration for FlareWebserviceClient #81
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
EmteZogaf
force-pushed
the
78-flarewebserviceclient-does-not-use-configured-java-trust-store-for-https
branch
from
18ef467
to
1152a07
Compare
EmteZogaf
force-pushed
the
78-flarewebserviceclient-does-not-use-configured-java-trust-store-for-https
branch
from
1152a07
to
08c1ab6
Compare
EmteZogaf
deleted the
78-flarewebserviceclient-does-not-use-configured-java-trust-store-for-https
branch
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.
These changes let the FlareWebserviceClient reuse all given tls certificate, proxy and authentication environment variables already used by the store client to have the same connection capabilities.
closes #78