Modernizing Applications with Apigee X recensioni

500 errors when executing curl

Ying L. · Recensione inserita 4 mesi fa

Don D. · Recensione inserita 4 mesi fa

Stefan H. · Recensione inserita 4 mesi fa

Don D. · Recensione inserita 4 mesi fa

Jose A. · Recensione inserita 4 mesi fa

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

Sam H. · Recensione inserita 4 mesi fa

Nermin S. · Recensione inserita 4 mesi fa

Feiyu L. · Recensione inserita 4 mesi fa

mj s. · Recensione inserita 4 mesi fa

Hay un problema al validar el sharedFlow

Cristina S. · Recensione inserita 4 mesi fa

智文 陳. · Recensione inserita 4 mesi fa

Anibal H. · Recensione inserita 4 mesi fa

智文 陳. · Recensione inserita 4 mesi fa

Sastry I. · Recensione inserita 4 mesi fa

Sastry I. · Recensione inserita 4 mesi fa

Parth S. · Recensione inserita 4 mesi fa

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. · Recensione inserita 4 mesi fa

Sourojit S. · Recensione inserita 4 mesi fa

Mark Leo J. · Recensione inserita 4 mesi fa

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. · Recensione inserita 4 mesi fa

Yixuan C. · Recensione inserita 4 mesi fa

두연 이. · Recensione inserita 4 mesi fa

Blanca Margarita L. · Recensione inserita 4 mesi fa

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. · Recensione inserita 4 mesi fa

Shruti C. · Recensione inserita 4 mesi fa