Search
Welcome to M-Files Empower – our new support experience. We'd love to hear what you think!Give feedback

Last updated on 21 June 2022

Admin
M-Files Electronic Signature (Compliance Kit)

Overview

Signom is changing some technical characteristics of its product. This article will describe the changes and their effect on M-Files integration. In a nutshell, no actions should be needed from M-Files side.

Solution

1)    The IP address of the Signom production endpoint www.signom.com will change around 17.5.2022. The actual change date will be further informed in https://status.signom.com/.
-> No action. This should not change anything on our side. We continue using the same URL.
-> In general, it will work, if the DNS address stays the same, but do note that due to DNS caching, it is possible that our customers experience a temporary break in the Signom service if they shutdown the old service simultaneously to opening the new one. This depends on how Signom handles this. It will affect all their customers, so I think that we should most likely be safe.
2)    Change in TLS 1.2 ciphersuites: some new ones are taken into use, some will be dropped.
-> No action. According to Signom, this is already in use in their test environment and our tests on it have been OK.
3)    The Signom test SOAP API endpoints have changed recently from 
https://test.signom.com/api/documentService
https://test.signom.com/api/userService
to
https://soap.test.signom.com/api/documentService
https://soap.test.signom.com/api/userService
-> No urgent action. Informing any Signom consultants is recommended. The change does not affect any production environment.

 

Still need help?

On this page