Additional Fields are now Mandatory for Tenant Registration
The following fields are now mandatory for tenant registration:
- Address
- City
- ZIP Code
- State/Province/Region*
* Mandatory if Country is set to United States, Canada, or Australia
Additional Fields are now Mandatory for Tenant Registration
The following fields are now mandatory for tenant registration:
* Mandatory if Country is set to United States, Canada, or Australia
The input fields for tenant registration, excluding the password field, will be trimmed. Leading and trailing spaces on input fields, excluding the password field, will be removed by the platform during registration.
If you have automation using the API for tenant registration and tenant updating you should modify your automation to account for this behavior.
See the Data Protection on Demand (DPoD) API for more information.
The following fields are being made mandatory for tenant registration when Country is set to United States, Canada, or Australia:
If you have automation using the API for tenant registration and tenant updating you should modify your automation to account for these new mandatory fields.
See the Data Protection on Demand (DPoD) API for more information about available endpoints and fields.
This change has been rescheduled to Tuesday February 8th 14:00 UTC to give customers more time to adjust their environments.
A knowledge base article with a full description of the change is available here. The article contains important information on mandatory changes for users on 10.0 or 10.1 client versions in North America.
This change introduces a new endpoint for validating the certificate status. Please ensure that operating systems hosting the client are able to validate the server certificate status (OCSP/CRL) using port 80.
Ensure that these certificate revocation lists (CRLs) are accessible from the client machine prior to the planned change on Tuesday February 8th 14:00 UTC to guarantee continuity of service.
Current CRL: http://crl.godaddy.com/gdig2s1-3235.crl
New CRL: http://crl.sectigo.com/SectigoRSAOrganizationValidationSecureServerCA.crl
Platform CRL: http://crl3.digicert.com/ssca-sha2-g7.crl
The following fields are being made mandatory for tenant registration:
If you have automation using the API for tenant registration and tenant updating you should modify your automation to account for these new mandatory fields.
See the Data Protection on Demand (DPoD) Public API for more information about available endpoints and fields.
Changed
The following Luna Cloud HSM service names have been changed:
The authentication method used by the 10.0 and 10.1 version of the Luna Cloud HSM client is being deprecated. Clients using this authentication will no longer be supported by the Luna Cloud HSM service after December 31, 2021.
We recommend you upgrade your client to the latest version at your earliest convenience. See Upgrading your client for more information.
CipherTrust Key Broker for Google Cloud EKM service users can now access their DPoD platform tenant. Users can log in to their tenant hostname URL to access DPoD platform features such as User Management, Tenant Management, and Reporting.
CipherTrust Key Broker for Google Cloud EKM service tenants do not have access to tenant features such as Subscriber Groups or Adding Services.
Removed
The PATCH /tenants/{id}/admin/reset and POST /tenants/{id}/admin/resetMfaToken operations have been removed from the DPoD Platform API.
Service provider administrators can no longer reset the password or MFA token of a user inside of a child tenant. Users can use the self-service resources in the DPoD platform or submit requests to an available administrator. See User Management for more information.
Deprecated
The authentication method used by the 10.0 and 10.1 version of the Luna Cloud HSM client is being deprecated. We recommend you upgrade your Luna Cloud HSM service clients to the latest version at your earliest convenience. Clients using this authentication mechanism will no longer connect to the service after December 31, 2021. Instructions for upgrading the client can be found in our documentation here.
