This website uses Cookies. Click Accept to agree to our website's cookie use as described in our Privacy Policy. Click Preferences to customize your cookie settings.
A client encountered an interesting error scenario. They recently got a
401 from an ouath validation failure, but the message was:
oauthV2.Oauth-ValidateToken.fault.causeUrlDecoding of the form
parameters from the request message failed. The form par...
We have a situation where a proxy will need to support both key or oauth
for authentication. Not a great situation, we realize. For the external
vendor utilizing key auth, they will have a restricted set of resources
available to them. We still will ...
Still curious as to why the oauth policy was having an issue with the
invalid/unencoded characters. Perhaps because of support for oauth
tokens as form parameters?
Sorry, I left out an important bit of information. The requests that
were failing did have illegal/un-encoded characters for
"application/x-www-form-urlencoded" but were legitimate for
application/json. I believe the offender was '%'. So, they create...
Here it is (scope removed). I'll admit that there's some elements in
here that are superfluous at the least. It would be curious if they were
part of the cause, though. The policy has historically worked as
expected.
Oauth-ValidateToken
false
Ver...
