使用 Apigee X 翻新應用程式 Reviews

500 errors when executing curl

Ying L. · Reviewed 4 months ago

Don D. · Reviewed 4 months ago

Stefan H. · Reviewed 4 months ago

Don D. · Reviewed 4 months ago

Jose A. · Reviewed 4 months ago

lab env wasn't set up properly to create apigee resources

Sam H. · Reviewed 4 months ago

Nermin S. · Reviewed 4 months ago

Feiyu L. · Reviewed 4 months ago

mj s. · Reviewed 4 months ago

Hay un problema al validar el sharedFlow

Cristina S. · Reviewed 4 months ago

智文 陳. · Reviewed 4 months ago

Anibal H. · Reviewed 4 months ago

智文 陳. · Reviewed 4 months ago

Sastry I. · Reviewed 4 months ago

Sastry I. · Reviewed 4 months ago

Parth S. · Reviewed 4 months ago

There were 2 bugs with this lab, 1 of which I was able to workaround. In the section "Test the API proxy" I was never able to successfully call the API after adding the <Authentication> section to the target endpoint xml. This was the error: curl -i -k "https://eval.example.com/bank/v1/atms/spruce-goose" HTTP/2 500 content-type: application/json x-request-id: 20034795-2f15-4147-9a9c-9f04562bade8 content-length: 344 date: Fri, 08 May 2026 17:47:50 GMT via: 1.1 google {"fault":{"faultstring":"Google token generation has failed. Please refer to https:\/\/cloud.google.com\/apigee\/docs\/api-platform\/reference\/policies\/service-callout-policy#runtime-errors for troubleshooting tips on GoogleTokenGenerationFailure errors.","detail":{"errorcode":"messaging.adaptors.http.filter.GoogleTokenGenerationFailure"}}} I tried troubleshooting the error but every possible cause for this error listed in the google documentation did not resolve this issue. The second bug I encountered was in the "Add a Service Callout policy" section which, if you follow the instructions exactly up to that point, you'll run into an issue where the "Add" button is disabled (grayed out) and it is impossible to add the policy. Oddly enough, this bug was resolved by refreshing the page in my browser and trying again.

Barclay I. · Reviewed 4 months ago

Sourojit S. · Reviewed 4 months ago

Mark Leo J. · Reviewed 4 months ago

You did not give service-[Project-Number]@gcp-sa-apigee.iam.gserviceaccount.com to have Role "Service Account Token Creator" and it will give error for <?xml version="1.0" encoding="UTF-8" standalone="yes"?> <TargetEndpoint name="default">   <Description/>   <FaultRules/>   <PreFlow name="PreFlow">     <Request/>     <Response/>   </PreFlow>   <PostFlow name="PostFlow">     <Request/>     <Response/>   </PostFlow>   <Flows/>   <HTTPTargetConnection>     <Properties/>     <URL>https://simplebank-rest-z6cmrsuiia-uk.a.run.app</URL>     <Authentication>       <GoogleIDToken>         <Audience>https://simplebank-rest-z6cmrsuiia-uk.a.run.app</Audience>       </GoogleIDToken>     </Authentication>   </HTTPTargetConnection> </TargetEndpoint>

Thanasit V. · Reviewed 4 months ago

Yixuan C. · Reviewed 4 months ago

두연 이. · Reviewed 4 months ago

Blanca Margarita L. · Reviewed 4 months ago

Apigee was not provisioned at the start, and trying to do so manually did not work with this error: constraints/gcp.resourceLocations Restarting the lab did make it work. However I was unable to finish final testing due to another error with api token generation.

Devin M. · Reviewed 4 months ago

Shruti C. · Reviewed 4 months ago