Como modernizar aplicativos com a Apigee X avaliações

Ahmed A. · Revisado há 3 months

yama G. · Revisado há 3 months

arzenmusic G. · Revisado há 3 months

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. · Revisado há 3 months

Pavan Kumar Gupta P. · Revisado há 3 months

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. · Revisado há 3 months

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

クレモン ゴ. · Revisado há 3 months

Carson P. · Revisado há 3 months

Praveen R. · Revisado há 3 months

Way too long!

Kenneth B. · Revisado há 3 months

Alexandru A. · Revisado há 3 months

Vinaya M. · Revisado há 3 months

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. · Revisado há 3 months

Francisco S. · Revisado há 3 months

Jonathan X. · Revisado há 3 months

CARLOS F. · Revisado há 3 months

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

Cristian V. · Revisado há 3 months

Vinaya M. · Revisado há 3 months

Salah E. · Revisado há 3 months

Ana Rosa S. · Revisado há 3 months

Ana Rosa S. · Revisado há 3 months

camilo e. · Revisado há 3 months

Rodrigo C. · Revisado há 3 months

Mnason Agung P. · Revisado há 3 months

Asmaa N. · Revisado há 3 months