-
Notifications
You must be signed in to change notification settings - Fork 113
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
Added support for HTTP TPC #2007
Conversation
Thanks for opening this pull request! The maintainers of this repository would appreciate it if you would create a changelog item based on your changes. |
74ce48a
to
79bd34b
Compare
This pull request introduces 2 alerts when merging 79bd34b into d3a946e - view on LGTM.com new alerts:
|
44407bc
to
0426fb9
Compare
This pull request introduces 2 alerts when merging 0426fb9 into d3a946e - view on LGTM.com new alerts:
|
0426fb9
to
56b2105
Compare
This pull request introduces 2 alerts when merging 56b2105 into d3a946e - view on LGTM.com new alerts:
|
56b2105
to
45c0cdc
Compare
This pull request introduces 2 alerts when merging 45c0cdc into d3a946e - view on LGTM.com new alerts:
|
45c0cdc
to
dd0093b
Compare
This pull request introduces 2 alerts when merging dd0093b into d3a946e - view on LGTM.com new alerts:
|
dd0093b
to
6024913
Compare
This pull request introduces 2 alerts when merging 6024913 into 7f7fab2 - view on LGTM.com new alerts:
|
6024913
to
028a0cd
Compare
This pull request introduces 2 alerts when merging 028a0cd into 7f7fab2 - view on LGTM.com new alerts:
|
Just trying to understand what this is for... |
Indeed, thanks for adding those references @butonic ! And for completeness, this is the report of the GSoC project related to this PR: https://gist.github.com/dynamic-entropy/ce664532ab28f8a13b7cf8f68e2d0f2a |
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.
Resurrecting this work to converge, so this PR could be merged and then we concentrate on the authentication part in another PR: can you please address those changes?
Then the authentication would touch the identity provider (in particular the oidc one), not this part, which I expect it to just work when Reva is driving the Third-Party Copy. Instead when Reva is the passive side, we'll have to possibly extend the code such that on GET
we validate the bearer token against different/multiple IDPs.
028a0cd
to
90365e2
Compare
Co-authored-by: Alex Unger <6905948+refs@users.noreply.github.com> Co-authored-by: Alex Unger <6905948+refs@users.noreply.github.com>
Also reworked example configuration for OIDC mapping as developed within WP4.4
Using for now a top-level group as IAM-ESCAPE seems to not be able to return optional subgroups as claims when querying the userinfo endpoint.
This module now supports the standard OIDC functionality when no mapping is defined, and the mapping via group claim when configured. In the future, oidc.go will be superseded by oidcmapping.go.
Plus some logging improvements
3ce4567
to
3450ac2
Compare
This pull request introduces 2 alerts when merging 3450ac2 into 96c9c09 - view on LGTM.com new alerts:
|
Co-authored-by: Giuseppe Lo Presti <giuseppe.lopresti@cern.ch>
Added support for HTTP Third Party Copy to the ocdav package.
HTTP-TPC is a protocol, based on HTTP, for copying an entity located on one server to a different server.
The main benefit is to allow for optimal the network use.
One typical optimisation is achieved by allowing the two servers to communicate directly so that the data representing the
entity is not relayed through the controlling client.
TODO:
[ ] Add ability to supply storage issued token-> this is addressed by mapping OIDC tokensCloses #1787