Apigee Lab 5: Protecting Against JSON Content Attacks Reviews

Ashley D. · Reviewed about 2 years ago

JOSE V. · Reviewed about 2 years ago

Suresh G. · Reviewed about 2 years ago

In task 3, when updating the App credentials to allow full access, the step to update the API Key stored in the cloudshell is omitted, meaning the later warning that an error may mean the API Key is just cached is incorrect, and it's actually because you're using the wrong API Key

Brian P. · Reviewed about 2 years ago

Jonathan M. · Reviewed about 2 years ago

Marcin C. · Reviewed about 2 years ago

Mirko G. · Reviewed about 2 years ago

super!

Robin S. · Reviewed about 2 years ago

Calvin Klark P. · Reviewed about 2 years ago

benjamin v. · Reviewed about 2 years ago

A gap with OAuth2 access token, the final step with replace shows { "error" : "invalid_resource", "error_description" : "The resource you requested does not exist." }

Yevhen B. · Reviewed about 2 years ago

Sergiy D. · Reviewed about 2 years ago

Dan K. · Reviewed about 2 years ago

Fernando Á. · Reviewed about 2 years ago

David B. · Reviewed about 2 years ago

Louis H. · Reviewed about 2 years ago

Nikita M. · Reviewed about 2 years ago

lab is mssing getting the Outh2 token, after the new credentials are created. This mean that step 3 failed and I had to removed the authentication step in the flow, to get around this

Alejandro G. · Reviewed about 2 years ago

Ivan R. · Reviewed about 2 years ago

invalid scenario - it assumes that api is secured by api key verification, while the predefined setup has oauth2 token verification

Tomasz K. · Reviewed about 2 years ago

error on instruction with keys

Dmytro S. · Reviewed about 2 years ago

Stefan S. · Reviewed about 2 years ago

Jose Luis H. · Reviewed about 2 years ago

Sanketh B. · Reviewed about 2 years ago

Iurii G. · Reviewed about 2 years ago