Please take a look at https://github.com/grpc/proposal/blob/master/A43-grpc-authorization-api.md and see if that addresses your questions.
On Wednesday, March 1, 2023 at 2:27:45 PM UTC-8 Eric Robins wrote: > Forgive the question if it's already been asked. I've been digging > through documentation on gRPC and how to secure it but I've been unable to > find anything at a very detailed level that explains what I guess I'd call > session management - the persistence of channels and underlying HTTP/2 > streams between a client and server where both may have been previously > authenticated. > > Using gRPC, how does a server know that it is still talking to the same > client it authenticated previously? In HTTP/1.1 session management is > achieved almost always through the use of cookies or other authorization > grants given to the client by the server that are represented back to the > server (in a header usually) every time a call is made during the active > session. How does this work in gRPC? > > Thanks in advance. Happy to go read more documentation if someone can > point me to it. > > Eric > -- You received this message because you are subscribed to the Google Groups "grpc.io" group. To unsubscribe from this group and stop receiving emails from it, send an email to grpc-io+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/grpc-io/5ef82106-6df0-4908-a565-b3d8ca37192fn%40googlegroups.com.
