关于“Apigee Lab 5: Protecting Against JSON Content Attacks”的评价

benjamin v. · 已于 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. · 已于 about 2 years前审核

Sergiy D. · 已于 about 2 years前审核

Dan K. · 已于 about 2 years前审核

Fernando Á. · 已于 about 2 years前审核

David B. · 已于 about 2 years前审核

Louis H. · 已于 about 2 years前审核

Nikita M. · 已于 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. · 已于 about 2 years前审核

Ivan R. · 已于 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. · 已于 about 2 years前审核

error on instruction with keys

Dmytro S. · 已于 about 2 years前审核

Stefan S. · 已于 about 2 years前审核

Jose Luis H. · 已于 about 2 years前审核

Sanketh B. · 已于 about 2 years前审核

Iurii G. · 已于 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. · 已于 about 2 years前审核

Leonardo C. · 已于 about 2 years前审核

Dwi A. · 已于 about 2 years前审核

Maybe this lab process lacks modify OAuth token

Tomoya T. · 已于 about 2 years前审核

NA

Arpit R. · 已于 about 2 years前审核

Freimy R. · 已于 about 2 years前审核

Dinesh B. · 已于 about 2 years前审核

Allison M. · 已于 about 2 years前审核

Mihai P. · 已于 about 2 years前审核