Apigee Lab 5: Protecting Against JSON Content Attacks Reviews

Felipe M. · Reviewed over 3 years ago

Midhun M. · Reviewed over 3 years ago

Alvaro L. · Reviewed over 3 years ago

Zhaorun J. · Reviewed over 3 years ago

Luis Rodrigo R. · Reviewed over 3 years ago

Jose F. · Reviewed over 3 years ago

Suprabhat V. · Reviewed over 3 years ago

Mounika T. · Reviewed over 3 years ago

Tauqeer A. · Reviewed over 3 years ago

Shaik H. · Reviewed over 3 years ago

Velpula V. · Reviewed over 3 years ago

Karthika K. · Reviewed over 3 years ago

solumtochukwu o. · Reviewed over 3 years ago

Madhusudan M. · Reviewed over 3 years ago

Pedro David M. · Reviewed over 3 years ago

Sergio E. · Reviewed over 3 years ago

The instructions for the lab were fine, but when testing the curl commands I kept getting 404 not found errors from apigee when trying to create an order.

Isaiah M. · Reviewed over 3 years ago

Joshua G. · Reviewed over 3 years ago

Tanya H. · Reviewed over 3 years ago

Jorenz Gabrielle Y. · Reviewed over 3 years ago

Mark V. · Reviewed over 3 years ago

Aditya N. · Reviewed over 3 years ago

Samir M. · Reviewed over 3 years ago

export API_KEY=$(curl -q -s -H "Authorization: Bearer $(gcloud auth print-access-token)" -X GET "https://apigee.googleapis.com/v1/organizations/${GOOGLE_CLOUD_PROJECT}/developers/joe@example.com/apps/retail-app" | jq --raw-output '.credentials[0].consumerKey'); echo "export API_KEY=${API_KEY}" >> ~/.profile; echo "API_KEY=${API_KEY}" { "error": { "code": 400, "message": "unable to parse organization from resource name", "status": "INVALID_ARGUMENT" } } The runtime instance was available but project was not set in the shell, had to manually add it "gcloud config set project {ID}"

César M. · Reviewed over 3 years ago

Jun Zhe N. · Reviewed over 3 years ago