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.
I think it's likely that you aren't sending the "SOAPAction" HTTP header
in the request to the Siebel backend. Without forwarding the SOAPAction
header, it's likely Siebel is inferring the incorrect soap action. You
can copy the SoapAction from the r...
> After completing "Step 7: Enable Control Plane Access," do I need to
upgrade the services that have already been deployed again? No, there is
no need to redploy. > For "Step 11 (Optional): Configure Workload
Identity," I am using a Kubernetes clust...
> I am unable to complete Step 7: Enable Control Plane access. The
"PATCH" HTTP method should be used, not POST. It's a documentation bug
we will correct. Please use: curl -X PATCH -H "Authoriztion: Bearer
$TOKEN"
'https://apigee.googleapis.com/v1/or...
Did you set a custom value for the "contractProvider" property?
https://cloud.google.com/apigee/docs/hybrid/v1.14/config-prop-ref.html#top-level
that is the value used to construct the URL that is resulting in a 404.
If you didn't chang this property...
