Adapt to OCM spec for remote shares #57166
Closed
+682
−29
Conversation
This file contains hidden or 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
…to use as bearer token
enriquepablo
requested review from
ArtificialOwl,
CarlSchwan,
leftybournes and
yemkareems
and removed request for
a team
CarlSchwan
reviewed
Dec 18, 2025
Co-authored-by: Carl Schwan <[email protected]> Signed-off-by: Enrique Pérez Arnaud <[email protected]>
Signed-off-by: Enrique Pérez Arnaud <[email protected]>
… get an access token to use as bearer token Signed-off-by: Enrique Pérez Arnaud <[email protected]>
Author
|
Big mess trying to sign-off old commits. I'm closing this and opening new clean PR. Sorry about this... |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Summary
This is a preliminary PR for discussion. If this goes through there are some things missing with which we'll be grateful to get some guidance:
There is also the question that for access tokens, we are keeping a reference to the corresponding refresh token in the uid field of the access token db record.
Also this depends on a pending PR for Guzzle:guzzle/guzzle#3310