This is the discussion thread for A59: gRPC Audit Logging.
https://github.com/grpc/proposal/pull/346
Please share your comments. Thank you.
--
You received this message because you are subscribed to the Google Groups
"grpc.io" group.
To unsubscribe from this group and stop receiving emails fro
Hi,
Does the FileWatcherCertificateProvider work
at
https://github.com/grpc/grpc/blob/master/include/grpcpp/security/tls_certificate_provider.h
for your use case? It's an experimental API but we plan to stabilize it
soon.
Best,
Luwei
On Tuesday, September 12, 2023 at 2:13:32 PM UTC-4 Amirsa
Hi,
I assume you are building gRPC with OpenSSL.
1. We do have some support for the Engine APIs
(https://github.com/grpc/grpc/blob/6534f0a6bfc1cfae6db931f9ee16f480de980374/src/core/tsi/ssl_transport_security.cc#L568)
of OpenSSL 1.0.2. Unfortunately, because the feature was implemented quite
a
to upgrade
> their grpc library to a new grpc version.
>
> Unless the community position is to let the users themselves build the
> grpc lib with whatever opssl version they prefer.
>
> If someone can shed some light on this, it would be greatly appreciated.
>
> Thanks
>
>
>
As of now, the CertificateProvider APIs I mentioned only come with two
built-in types, StaticData and FileWatcher. So unfortunately, the custom
logic you'd like isn't supported. That said, we are considering whether we
will support user-defined CertificateProvider implementations. This is yet
t
gRPC-python wraps gRPC-Core as they are in the same repo. So if you go to
the specific git tag,
e.g. https://github.com/grpc/grpc/tree/v1.58.0/third_party, you can find
the commit of the BorgingSSL dependency (boringssl-with-bazel ...). In this
case of 1.58.0,
it's
https://github.com/google/b
Hi Rameshreddy,
Looks like you want to log things that are not currently available in the
audit context we have defined. Would you mind opening an issue on GitHub
for such a feature request?
Best,
Luwei
On Friday, January 31, 2025 at 2:56:00 PM UTC-8 Rameshreddy Mudhireddy
wrote:
> please ig
Hi Ramesh,
I am not sure if I fully understand your problem. Are you restarting the
gRPC server within your process? If so, I think you need to call
RegisterAuditLoggerFactory again, if you didn't.
Best,
Luwei
On Sunday, July 6, 2025 at 5:24:32 PM UTC-7 Rameshreddy Mudhireddy wrote:
> Hi grpc-
The intent of the Register... API is that all audit loggers that may be
used should have been registered from the very beginning, because custom
loggers can possibly be custom implementations which need to be compiled
and built into the application binary. So I think the correct way to run
your
