Impact after upgrading to the Zurich version

[ayano]

We are integrating ServiceNow with an external tool using an API management tool called 3scale. However, after upgrading ServiceNow to the Zurich version, the 3scale API authentication no longer works, and we receive an HTTP 500 error indicating that the URL is incorrect.

With the Yokohama version, the same 3scale URL and API key worked without any issues for this API connection, but after upgrading to the Zurich version, it no longer works. 

Is it possible that the ServiceNow instance IP address has changed?
Do you know what could be causing this issue?

[Tanushree Maiti]

Hi @ayano 

Here is probable cause:

1. It could be the case - your installed plugin not compatible with Zurich version. Update the plugin version , if needed.

2. System Logs and Debugging: The 500 error is a generic server-side error. Review the detailed system logs in ServiceNow for more specific error messages, which can pinpoint the exact cause (e.g., an SSL handshake failure, missing required input/output, or other configuration errors)

3. If your API , you are using any encryption , just fyi,  Zurich release deprecates the 3DES encryption standard and defaults to AES for the GlideEncrypter API.

4. Validate Role: As Zurich release is more strict on security -

   Review existing ACLs to ensure the integration account has the necessary read/write access to the required tables and fields.

5. Make sure in your http request , you are passing the parameter properly.

[Ankur Bawiskar]

@ayano 

IP won't change usually after upgrade.

are you connecting via MID Server or directly to that API?

[ayano]

Hi @Ankur Bawiskar  san,
Thank you for your reply.
I'm connecting directly to the API.

[Ankur Bawiskar]

@ayano 

did you compare the API request how it was looking before upgrade and after?

something extra is getting appended in URL leading to this issue?

💡 If my response helped, please mark it as correct ✅ and close the thread 🔒— this helps future readers find the solution faster! 🙏