Hi there,
However, in the meantime I was wondering if there is any other per connection context that is accessible to interceptors with an insecure server?
Similar to how grpc::AuthContext may be modified within AuthMetadataProcessor.
I having been using the auth context as a makeshift cache for storing per connection authentication (rpc metadata username/password) results, to prevent multiple expensive calls to my custom authentication process. I now require the same for insecure servers.
Thanks,
Dylan