This website uses Cookies. Click Accept to agree to our website's cookie use as described in our Privacy Policy. Click Preferences to customize your cookie settings.
Hi pato17, To know more about the required payload format, please review
the PubSub REST API docs here. Here's a Service Callout that you could
use to send base64-encoded messages that adhere to the PubSub API spec:
POST { "messages": [ { "data":...
The idea to use WIF to circumvent cross-project SA usage is worth
exploring. You don't have to have an external OIDC provider. Instead,
you can use the GenerateJWT policy in Apigee to mint a new token that
will can be trusted by a workload identity p...
Hi Aruna! The External Callout policy requires a specific gRPC proto
implementation. This feature may only be helpful for you if you're open
to implementing this Apigee proto on the server side. Based on your use
case, I believe you're looking for gR...
Hi Raghu! Currently, we do not support OIDC for single sign-on. SAML is
the preferred SSO mechanism for most of our customers. However, our
product team is exploring expanded SSO options for future releases.
The documentation link that you're referring to describes all the
available options to check health status of Apigee. The
environment-level health check endpoints are the best option to make
sure a given environment (and proxies that have been deploy...
