Enable access to EOS via tokens over gRPC (e.g. for guest accounts) #4934
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
|
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. |
jessegeens
force-pushed
the
feat/grpc-generate-eos-token
branch
3 times, most recently
from
b7deeb4
to
58bb028
Compare
diocas
requested changes
Nov 13, 2024
jessegeens
force-pushed
the
feat/grpc-generate-eos-token
branch
from
58bb028
to
bf72c71
Compare
jessegeens
force-pushed
the
feat/grpc-generate-eos-token
branch
from
bf72c71
to
a5ad680
Compare
diocas
approved these changes
Nov 14, 2024
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.
As a guest account, accessing a file shared with you relies on a token that is generated on behalf of the resource owner. This method,
GenerateToken, was not yet implemented in the EOS gRPC client. Additionally, the HTTP client did not yet take tokens into account.