FELIX-6179 - Fix Jetty Client Authentication #199
Closed
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
|
R: @jbonofre |
|
I think we should upgrade to 9.4.20. |
|
We updated to 9.4.20 yesterday and just started the vote to release it |
|
@cziegeler I rebased the PR so that it still includes the issue to fix Jetty client authentication, please take a look. |
|
@coheigea Thanks, could you please open an Apache Felix Jira issue for this and link your PR in that issue? |
coheigea
changed the title
coheigea
changed the title
|
@cziegeler Yes done |
|
Thanks, I will take a look. |
rotty3000
pushed a commit
to rotty3000/felix
that referenced
this pull request
Sep 16, 2019
This closes apache#199 apache#190 git-svn-id: https://svn.apache.org/repos/asf/felix/trunk@1866430 13f79535-47bb-0310-9956-ffa450edef68
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.
Jetty Client authentication does not work, see: jetty/jetty.project#3554. Changing to use SslContextFactory.Server as in the patch fixes this issue.