Why don't all logged-in Request objects have a token field?

[michielbdejong]

I see the WhoAmIRequest lets you specify the token which you received from AuthenticateResponse, but none of the other method Request objects do.

I see revad throws "core access token not found" when you try to do for instance a ListReceivedOCMShared call.
Is there another way to pass the token in a grpc request?

[michielbdejong]

Ah, I think I found something:

• https://grpc.io/docs/guides/auth/
• https://github.com/cs3org/reva/blob/master/pkg/sdk/session.go#L99-L103

[michielbdejong]

Sending a token header combined with insecure channel credentials is not supported by the node implementation of grpc.
I'll find out how the go client does it. Maybe it adds the x-access-token header in an interceptor, instead of through officia l grpc credentials?

[michielbdejong]

Hm, it seems that https://github.com/cs3org/reva/blob/v1.11.0/pkg/sdk/session.go#L125-L127 sets the header when communicating over http, but how does it get set when communicating over grpc?

[michielbdejong]

Ah, I think I got it! https://github.com/cs3org/reva/blob/v1.11.0/cmd/reva/grpc.go#L36

[michielbdejong]

Not sure why it calls both ContextSetToken and AppendToOutgoingContext

[michielbdejong]

https://stackoverflow.com/a/37551218/680454 should do something similar in node.

[michielbdejong]

Yes! OK, I got it now, will create a PR to update https://github.com/cs3org/node-cs3apis#example-usage.