Why is this happening?
Validic wants to ensure our customers’ data is protected appropriately at all times. To do so, we occasionally need to update our software and systems to meet certain standards set by various industry leaders. To that end, Validic will require customers accessing our system beginning September 21, 2015 to be compatible with the SHA-2 standard.
What does this mean for me?
After Validic enables our new security certificate on September 21, 2015, any connections that do not support SHA-2 will either receive visual errors or data will not be returned at all. This includes browsers and any integrations to the Validic API using unsupported encryption protocols.
What action do I need to take?
In order to maintain seamless access to the Validic API, you need to ensure browsers and integrations connecting to Validic support SHA-2. If your browser or integration does not support SHA-2 after we make this change, then your users will NOT be able to access Validic. We recommend you begin planning to support SHA-2 protocol as soon as possible.
How can I test my application?
Validic has established a test server at https://api-edge.validic.
Validic recommends testing your application against the test API server (https://api-edge.validic.com)
What should I do if my test fails?
The most likely cause of failure is that our certificate’s Signing Authority is not in your CA store. Below are some links based on different technologies:
Java – https://docs.oracle.com/
.NET – https://msdn.microsoft.com/en-
Ruby – https://railsapps.github.io/
NodeJS - https://nodejs.org/docs/v0.7.