Veeva Vault modifies the set of supported TLS cipher suites to provide a better developer experience. For example, we may remove weak ciphers or change cipher priority order to utilize stronger ciphers. These changes may affect custom integrations, but Vault UI users are not affected.
Prior to any changes, Veeva will contact all customers with affected integrations so that they can test their integrations. Customers can test the new ciphers on a limited release sandbox Vault.
If you have questions, please contact Veeva Support.
Release Date: 24R3.2; Dec 13, 2024
Beginning with the 25R1 release, Vault will add support for TLS 1.3 and no longer support CBC cipher suites:
ECDHE-RSA-AES256-SHA384
ECDHE-RSA-AES128-SHA256
These changes may affect some custom integrations, but not users accessing Vault with a supported browser.
All customers with affected integrations will be contacted directly by Veeva Developer Services.
Release Dates:
In this release, Vault will no longer support TLS1.0 and TLS1.1 for FTPS. These changes may affect custom integrations, but Vault UI users are not affected.
Release Dates:
Beginning with the 21R1 release, Vault will no longer support the following cipher:
TLSv1.2/DHE-RSA-AES256-GCM-SHA384
TLSv1.2/ECDHE-RSA-AES256-GCM-SHA384
TLSv1.2/ECDHE-RSA-AES256-SHA384
TLSv1.2/ECDHE-RSA-AES128-GCM-SHA256
TLSv1.2/ECDHE-RSA-AES128-SHA256
Release Dates:
Beginning with the 20R3 release, Vault will no longer support the following ciphers:
TLSv1.2/DHE-RSA-AES256-SHA256
TLSv1.2/DHE-RSA-AES128-GCM-SHA256
TLSv1.2/ECDHE-RSA-AES128-SHA
The following cipher will be moved to the bottom of the cipher suite priority list:
TLSv1.2/DHE-RSA-AES256-GCM-SHA384
TLSv1.2/ECDHE-RSA-AES256-GCM-SHA384
TLSv1.2/ECDHE-RSA-AES256-SHA384
TLSv1.2/ECDHE-RSA-AES128-GCM-SHA256
TLSv1.2/ECDHE-RSA-AES128-SHA256
TLSv1.2/DHE-RSA-AES256-GCM-SHA384