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

benjamin v. · Revisado há about 2 years

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. · Revisado há about 2 years

Sergiy D. · Revisado há about 2 years

Dan K. · Revisado há about 2 years

Fernando Á. · Revisado há about 2 years

David B. · Revisado há about 2 years

Louis H. · Revisado há about 2 years

Nikita M. · Revisado há about 2 years

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. · Revisado há about 2 years

Ivan R. · Revisado há about 2 years

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

Tomasz K. · Revisado há about 2 years

error on instruction with keys

Dmytro S. · Revisado há about 2 years

Stefan S. · Revisado há about 2 years

Jose Luis H. · Revisado há about 2 years

Sanketh B. · Revisado há about 2 years

Iurii G. · Revisado há about 2 years

The auth mechanism is not configured properly. The lab shows commands for API Key Auth but Token verification for client credentials is implemented in the preloaded assets. We should correct the commands so they reference oauth cc or change the auth mech from the preloaded assets.

Ricardo S. · Revisado há about 2 years

Leonardo C. · Revisado há about 2 years

Dwi A. · Revisado há about 2 years

Maybe this lab process lacks modify OAuth token

Tomoya T. · Revisado há about 2 years

NA

Arpit R. · Revisado há about 2 years

Freimy R. · Revisado há about 2 years

Dinesh B. · Revisado há about 2 years

Allison M. · Revisado há about 2 years

Mihai P. · Revisado há about 2 years