-
Notifications
You must be signed in to change notification settings - Fork 240
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
refactor: moved security checks in protocol service layer #3668
refactor: moved security checks in protocol service layer #3668
Conversation
987a239
to
a55deff
Compare
Codecov ReportAttention:
❗ Your organization needs to install the Codecov GitHub app to enable full functionality. Additional details and impacted files@@ Coverage Diff @@
## main #3668 +/- ##
============================================
- Coverage 71.68% 4.46% -67.22%
- Complexity 0 236 +236
============================================
Files 916 917 +1
Lines 18415 18413 -2
Branches 1043 1041 -2
============================================
- Hits 13200 823 -12377
- Misses 4757 17573 +12816
+ Partials 458 17 -441 ☔ View full report in Codecov by Sentry. |
a55deff
to
b655f91
Compare
...e-services/src/main/java/org/eclipse/edc/connector/service/protocol/BaseProtocolService.java
Outdated
Show resolved
Hide resolved
87a1ffd
to
3d36175
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🚀
What this PR changes/adds
Implements the refactor outlined in DR #3665
Why it does that
Decoupling the net protocol from the security checksm which are now delegated to the protocol service layer.
This also will allow use to attach contextual information to the verification process.
Further notes
In this PR since we are pushing here the invocation of the
IdentityService
we don't know the audience here/ The audience removal will be tackle in subsequent PRs.IdentityService
that relies on this parameter would not work for the time being.Linked Issue(s)
Closes #3667
Please be sure to take a look at the contributing guidelines and our etiquette for pull requests.