Apigee Lab 5: Protecting Against JSON Content Attacks avaliações

Jose F. · Revisado há over 3 years

Suprabhat V. · Revisado há over 3 years

Mounika T. · Revisado há over 3 years

Tauqeer A. · Revisado há over 3 years

Shaik H. · Revisado há over 3 years

Velpula V. · Revisado há over 3 years

Karthika K. · Revisado há over 3 years

solumtochukwu o. · Revisado há over 3 years

Madhusudan M. · Revisado há over 3 years

Pedro David M. · Revisado há over 3 years

Sergio E. · Revisado há over 3 years

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

Joshua G. · Revisado há over 3 years

Tanya H. · Revisado há over 3 years

Jorenz Gabrielle Y. · Revisado há over 3 years

Mark V. · Revisado há over 3 years

Aditya N. · Revisado há over 3 years

Samir M. · Revisado há over 3 years

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

Jun Zhe N. · Revisado há over 3 years

Heidi E. · Revisado há over 3 years

Jose Alfron B. · Revisado há over 3 years

Clarisse Myles P. · Revisado há over 3 years

Francis G. · Revisado há over 3 years

Akshay B. · Revisado há over 3 years