04-25-2017 09:40 AM
I recently had an issue where the password contained “&” in it and the end point which is a Auth Token server failed to validate it.
I was not sure if the Auth Server failed to receive it in proper format or if our snap was transmitting it improperly.
The workaround was to change the password replacing the “&” with another character such as “_”.
Please note this for any REST related problems.
04-25-2017 09:51 AM
@nganapathiraju what kind of authentication scheme was this (OAuth? Form data?) If the password was in the request body or a query parameter, then the ampersand character would probably need to be escaped.
04-25-2017 09:57 AM
Yes I forgot to mention.
It was Oauth Authentication but it requires the credentials in the Post Body.