Event management custom Push Connector fails with no valid Signature error if MID Server restarts

[Pranita Bahugun]

Hello everyone,

I have configured a Custom Push Connector which pushes events from a third party monitoring tool to ServiceNow. The integration is setup correctly but whenever the MID Server restarts the certificate which is setup in third party tool to connect with the MID Server fails and connection is broken. When we verified the certificate on each restart the certificate is changed and this will cause issue for continuous monitoring.

Has anyone come across this scenario or issue? Any fix we can apply so that the certificate do not gets changed on each MID Server restart.

Thankyou for your attention.

Any quick help is very much appreciated.

Best Regards,

Pranita Bahuguni

[Abbas_5]

Hello @Pranita Bahugun,

The "no valid signature" error after a MID Server restart with a custom push connector for event management in ServiceNow is likely due to certificate issues. The MID Server may be re-generating certificates on restart, which invalidates the previous ones used by the connector. 

Troubleshooting Steps:

1. 1. Certificate Validation:

   • Verify that the certificate used by the third-party tool is still valid after the MID Server restart. 
   • Ensure the certificate is trusted by the MID Server. 
2. 2. MID Server Configuration:

   • Check the MID Server's configuration for certificate handling. 
   • Review the mid.property file, especially properties related to certificates and authentication. 
3. 3. Certificate Storage:

   • If possible, configure the MID Server to use a persistent certificate store instead of regenerating certificates on each restart. 
4. 4. MID Server Logs:

   • Examine the MID Server logs for any errors related to certificate validation or authentication. 
5. 5. Firewall and Proxy:

   • Ensure the firewall and proxy configurations allow the MID Server to access the necessary resources, including certificate validation servers (e.g., OCSP). 
6. 6. Authentication:

   • If basic authentication is used, verify that the credentials are correct and haven't been changed during the restart. 
7. 7. Time Synchronization:

   • Check if the MID Server's time is synchronized with the ServiceNow instance. Time differences can affect certificate validation. 

Additional Considerations:

• OCSP Check:

  The MID Server might perform Online Certificate Status Protocol (OCSP) checks. Ensure that the necessary connections are allowed through the firewall. 
• Proxy Configuration:

  If a proxy is used, ensure it's configured correctly for the MID Server and that it doesn't block certificate validation requests. 
• MID Server Version:

  Make sure the MID Server is up to date with the latest version, as older versions might have known issues with certificate handling

  If this is helpful, please hit the thumbs up button and accept the correct solution by referring to this solution in future it will be helpful to them.

  Thanks & Regards,

  Abbas Shaik