Sorry for the trouble. I made some changes for I was testing a new authentication strategy we are prototyping and I expected users would need to reconnect their app for the changes to be reflected. Let me roll them back. Will ping you in a minute
Can you try to reconnect SN again please and lmk how it goes?
back in business - thank you! fwiw, when I went to go re-connect I found it was already reconnected (that magic is fine with me!) so instead I just replayed the failed events from earlier, and they went through no problem, so we’re good for the moment!
Posted thread to Discourse: How to Resolve ServiceNow Connector Reconnection Issues Due to Missing Authentication Fields and OAuth Errors?
Hi there - did some new auth changes get pushed? ServiceNow disconnected again and I can’t reconnect it. I get to the point where I’m able to see the “Allow” button in ServiceNow, but when I click it, either nothing happens, I get a totally white screen, or sometimes I get this error: OAuthProblemException{error=‘invalid_request’, description=‘Missing response_type parameter value’, uri=‘null’, state=‘null’, scope=‘null’, redirectUri=‘null’, responseStatus=0, parameters={}}
Hi I checked the interface for apps and there hasn’t been any chances to ServiceNow app recently. Let me take a deeper look on what might be going on
ok! I also just got this screen after another attempt, with this link in case it helps to track down anything in logs! https://pipedream.com/popup/auth/error?retry_link=https%3A%2F%2Fapi.pipedream.com%2[…]2Foa_g2oiqA%3Foauth_flow_id%3De8346084ff29ed6b68850698dbab66e2
I checked, the ServiceNow connector seems to be working properly, i tried from our dev instance. I’ve requested help interally to get error logs from recent user connections to see if I there is any hint there.
Indeed, things seem to have snapped back into place - thank you very much!