This topic was automatically generated from Slack. You can find the original thread here.
Hi there - can anyone advise on issues I’m having reconnecting my ServiceNow connector? I got a notification that it must be reconnected, and the screen that comes up only lets me enter the instance name - previously there were fields for the client ID / client secret, etc. to handle authentication, but those other fields are just not there anymore. When I enter the instance name and click continue, I get an oauth error on the SN side because the credentials aren’t being passed.
Tried again, the fields did show up this time - but the URL that was generated was missing some parameters, I think. The parameters should be client_id, code_challenge, code_challenge_method, redirect_uri, response_type and state. The URL generated was indeed missing code_challenge and code_challenge_method.
Hi - my ServiceNow account has disconnected again, and upon trying to reconnect I’m back to square one; only a box to enter the instance name, not the client credentials.
Hi Kevin we made some recent highly requested updates to our ServiceNow app to simplify the auth process for users. Can you try to reauthorize using the new auth flow so that you can reestablish the connection? Just add your instance name and it’ll prompt you to sign into your ServiceNow instance to reconnect.
I still get an error telling me the client credentials are invalid. Does the new process require any changes on the ServiceNow side? I read the Pipedream docs page and it still seems to reflect the need for having client credentials involved.
Thanks for sharing screenshots, I’ll review this today and follow up with instructions on resolving this. For now, can you submit a bug report issue here and prioritize it: Sign in to GitHub · GitHub
I’m going to DM you a video of what happens, since the password is displayed in clear text I don’t want to put it in a public thread. But, in summary - it doesn’t seem to work. I enter the instance, username and password and click test connection. The connection test succeeds, but when I do it for real, it spins a bit, then dismisses the modal window, but the connector is still not authorized. I refreshed the page to make sure.
Hi , this is Sergio. I am with the integrations team here at Pipedream.
Sophia is telling me you are experiencing an code_challenge error when connecting to the ServiceNow app
So, yesterday we reverted the ServiceNow app to our previous authentication setup where we ask for client id / client secret.
Since these clients are not meant to be available publicly to any ServiceNow user, we didn’t set up PKCE in the oauth 2.0 flow of the app.
In this case, would you be able to modify your OAuth 2.0 authorization code client (via All > System OAuth > Inbound Integration) such that the “is public client” remains unchecked?
This will make your client match the oauth flow configuration in Pipedream
I’d appreciate if you could try this and let me know if this worked
Hi, me again! Our SN account has once again disconnected, and I can’t reconnect with the new auth flow that contains only the instance name. The error message I get on the SN side is “unauthorized_client: The client credentials provided (those of the service you are using) are either not valid or not trusted” - I checked the Pipedream docs (ServiceNow - Pipedream) just to see if maybe there was guidance on ServiceNow setup for the new flow - but it still seems to reference the old client id/secret settings. Let me know what we can do next!
success, thank you !
