Modernizing Applications with Apigee X Reviews

Ahmed A. · Reviewed 3 months ago

yama G. · Reviewed 3 months ago

arzenmusic G. · Reviewed 3 months ago

Problema Detectado: En el paso de prueba del proxy bank-v1, los estudiantes reciben un error HTTP 500 con el código de error messaging.adaptors.http.filter.GoogleTokenGenerationFailure al intentar llamar al proxy desde la VM de prueba. Causa Raíz: El manual del lab omite un paso crítico de configuración de IAM. Para que Apigee pueda generar un token de identidad (OIDC) utilizando una cuenta de servicio personalizada (como apigee-internal-access), el Service Agent de Apigee debe tener permiso explícito para impersonar dicha cuenta. Sin este permiso, la generación del token falla. Sugerencia de Corrección: Se debe agregar un nuevo paso en la sección "Create a service account for the Apigee API proxy", justo después de otorgar el rol de roles/run.invoker.

Lorenzo S. · Reviewed 3 months ago

Pavan Kumar Gupta P. · Reviewed 3 months ago

I got stuck in this lab twice while following the instructions exactly at Task 3 step 15 and Task 4 service callout, and repeating the tasks again.

Eric H. · Reviewed 3 months ago

There was a bug when creating policy, the "Add" button stayed grayed out I had to force refresh browser to clear the problem

クレモン ゴ. · Reviewed 3 months ago

Carson P. · Reviewed 3 months ago

Praveen R. · Reviewed 3 months ago

Way too long!

Kenneth B. · Reviewed 3 months ago

Alexandru A. · Reviewed 3 months ago

Vinaya M. · Reviewed 3 months ago

In Task 2, in "Test the API proxy", even after setting the authentication settings for Target endpoints default, I always got this error: HTTP/2 500 content-type: application/json x-request-id: 88fbad5f-a679-4d5f-8dce-bc10d7adad9a content-length: 344 date: Wed, 03 Jun 2026 05:37:31 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"}}} This happened twice (unfortunate because this lab takes so much time). Bypassed this issue by disabling authentication on the cloud run service.

Michelle O. · Reviewed 3 months ago

Francisco S. · Reviewed 3 months ago

Jonathan X. · Reviewed 3 months ago

CARLOS F. · Reviewed 3 months ago

Task 4 didn't work even though I followed all the steps

Cristian V. · Reviewed 3 months ago

Vinaya M. · Reviewed 3 months ago

Salah E. · Reviewed 3 months ago

Ana Rosa S. · Reviewed 3 months ago

Ana Rosa S. · Reviewed 3 months ago

camilo e. · Reviewed 3 months ago

Rodrigo C. · Reviewed 3 months ago

Mnason Agung P. · Reviewed 3 months ago

Asmaa N. · Reviewed 3 months ago