关于“利用 Apigee X 保护 API”的评价

Sourojit S. · 已于 11 days前审核

Rohit K. · 已于 11 days前审核

Brayan Alejandro F. · 已于 11 days前审核

Jessica B. · 已于 11 days前审核

Manjunatha R. · 已于 11 days前审核

Neel P. · 已于 12 days前审核

Stefan H. · 已于 12 days前审核

Parth S. · 已于 12 days前审核

Milica A. · 已于 12 days前审核

Milica A. · 已于 13 days前审核

Something should be done about this, it happens on every apigee lab: curl -i -k -H "Authorization: Bearer ${JWT_TOKEN}" -X GET "https://eval.example.com/bank/v1/customers" HTTP/2 500 content-type: application/json x-request-id: e4f12ccd-a5c0-4de5-81e5-57afec486153 content-length: 344 date: Mon, 11 May 2026 20:02:11 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"}}}

Barclay I. · 已于 13 days前审核

Jose A. · 已于 13 days前审核

Milica A. · 已于 13 days前审核

Feiyu L. · 已于 14 days前审核

Roman P. · 已于 14 days前审核

智文陳. · 已于 15 days前审核

Sastry I. · 已于 15 days前审核

Arindam K. · 已于 15 days前审核

Riccardo B. · 已于 15 days前审核

Impossible to complete within allotted lab time due to Aipgee provisioning taking >50 minutes for Task 4

Ian H. · 已于 17 days前审核

Jan Norman S. · 已于 17 days前审核

Yixuan C. · 已于 17 days前审核