To continue providing optimal security for our customers, AssureSign will no longer support users with TLS versions 1.0 and 1.1. All AssureSign users must upgrade to TLS version 1.2 by 5/18/2016.
Please note that per this announcement, we implemented this change in our Sandbox environment (SB.AssureSign.net) this morning.
- This is an application level change that might require action on your part by 5/18/2016.
- You will need to be using a browser that supports TLS 1.2 to continue using AssureSign. If you are unsure whether your browser supports it, you can verify this by clicking here and ensuring that the page shows "Your user agent has good protocol support" under theProtocol Support section. If you do not see this message, please contact your IT department or AssureSign Support for further assistance.
- If you currently use any of the following AssureSign solutions, please ensure you are running the latest available version:
- Any clients utilizing any custom or 3rd party applications or solutions with AssureSign, should review their systems to ensure that they can communicate with AssureSign via the TLS 1.2 protocol.
At AssureSign we are committed to providing our customers with top security and performance features. TLS versions 1.0 and 1.1 suffer from several cryptographic flaws which could allow security to be bypassed. Please ensure you have undertaken any necessary steps as outlined above to ensure you are using TLS 1.2 by 5/18/2016.
In addition to the TLS change mentioned above, users of our NA1 production environment should make note that the server certificate for NA1.AssureSign.net will also be changing on 5/18/2016. This is being done as part of a larger initiative for us to standardize on a single SSL server certificate vendor.
This certificate change should be transparent to most users, so no changes should be necessary for signers and most client applications. Any clients that previously installed the root and intermediate certificates for integration purposes may require modifications to be made to trust the new certificate chain. If access to the intermediate certificates is required in advance, please contact support. The new certificate will be valid until April 11th, 2018.