OAuth token generation fails intermittently when integration user's password contains an ampersandIssue Trying to generate an OAuth Access token for an inbound api call to SeriviceNow is failing. Symptoms Token requests to the oauth_token.do endpoint succeed on some attempts and fail on others.Postman returns a 302 redirect followed by a logout. Facts Token endpoint: https://<instance-name>.service-now.com/oauth_token.doAuthentication method: OAuth Release Any Cause When the integration user password contains an ampersand (&), the character is read as an additional parameter in the token request instead of as part of the secret value. This causes authentication to fail intermittently. Resolution 1. Click on the 'Generate' UI action on the sys_user record of the user used for generating the token to set the password until a value without an ampersand is generated.2. Alternatively, manually set a new password ensuring it does not contain any ampersands.