Has anyone run into an issue where Token Based Aut...
# general
j
Has anyone run into an issue where Token Based Authentication will fail on a GET RESTlet request if the URL has any kind of parameter encoding? For example, if we have a URL parameter without encoding "&subsidiaryIdCsv=3,2,9" our request will run successfully. If we try to properly encode the values "&subsidiaryIdCsv=3%2C2%2C9" our request will fail with the following error: "error": { "code": "INVALID_LOGIN_ATTEMPT", "message": "Invalid login attempt." } If we switch back to NL Auth authentication the request runs without issue using encoded parameter values