You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, the FulcioClient communicates via gRPC. While this is acceptable when communicating with the Public Good Instance (prod/staging), gRPC may not be exposed/running in self hosted deployments, rendering the client to being unusable.
Add support for standard HTTP communication to Fulcio which could be implemented as an entirely separate function/method or as a fallback when gRPC is not available
The text was updated successfully, but these errors were encountered:
That's interesting, I thought fulcio always enables the grpc endpoint with an http proxy. @bobcallaway? Can you share your config. If it truly makes sense to use http, then we can figure out how to enable this.
Yeah, there was an http client but we removed it since there was no perceived use for it, but that appears to be untrue. Happy to review a PR, but that's kinda low priority for me. Maybe a few steps via separate PRs
Create a FuclioClient interface that both the grpc client and http client would implement.
Revive the HttpClient (and use it the v2 rest api for fulcio -- not v1)
Figure out how to enable this in the KeylessSigner (I don't know if automatic is ideal, maybe just a system property?)
Currently, the FulcioClient communicates via gRPC. While this is acceptable when communicating with the Public Good Instance (prod/staging), gRPC may not be exposed/running in self hosted deployments, rendering the client to being unusable.
Add support for standard HTTP communication to Fulcio which could be implemented as an entirely separate function/method or as a fallback when gRPC is not available
The text was updated successfully, but these errors were encountered: