Changed behavior of java api client to avoid 401 problems #2553 #2560
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
de-jcup
changed the title
- created unit test to reproduce problem (wire mock test) - changed login behavior, instead of using a authenticator object we use now a request interceptor and set the basic auth header directly - removed server url and trust all setters - introduced new constructor inside abstract SecHub client to have fields inside mocked client as well
de-jcup
force-pushed
the
feature-2553-handle-java-client-auth-problems
branch
from
027180d to
142f9cc
Compare
Jeeppler
suggested changes
Sep 26, 2023
Jeeppler
approved these changes
Sep 27, 2023
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.
This PR