Fixed Issue: Resolved a problem that prevented some users from viewing Luna Cloud HSM snapshots. This fix enhances the user experience and ensures that all snapshots are accessible as intended.
Fixed Issue: Resolved a problem that prevented some users from viewing Luna Cloud HSM snapshots. This fix enhances the user experience and ensures that all snapshots are accessible as intended.
Thales is changing the Identity Provider (IDP) used in the DPoD platform to Thales OneWelcome Identity Platform. This enables the platform to provide modern authentication options to users as well as simplifying logins for users that manage multiple tenants on the platform.
Thales will migrate each region per the schedule below.
A maintenance window with exact timing for the migrations and service impacts will be shared through the DPoD Status Page. We recommend subscribing to the status page to be notified of any updates or schedule changes.
After the migration DPoD will be accessible through the new login URL - https://welcome.dpondemand.io, and users will receive instructions to register a new MFA OTP with their device on their first login.
If you have additional questions regarding the IDP migration to One Welcome, please consult the DPoD IDP Migration FAQ on thalesdocs.com.
Early in 2025 Thales Data Protection on Demand (DPoD) will be changing the Identity Provider (IDP) used in the DPoD platform to Thales OneWelcome. New Certificate authority CRLs and OCSPs will be added.
For more information about the IDP migration see the DPoD IDP Migration FAQ.
Early in 2025 Thales Data Protection on Demand (DPoD) will be changing the Identity Provider (IDP) used in the DPoD platform to Thales OneWelcome. To ensure continued network connectivity between your Luna Cloud HSM client and the service partition please ensure that you update your include lists to allow the Thales OneWelcome fully qualified domain names. The Luna Cloud HSM data centers are configured with floating IP addresses and as a result of this configuration we do not support using static IP addresses or hardcoded IP addresses to access the services.
For more information about the IDP migration see the DPoD IDP Migration FAQ. For more information about configuring and troubleshooting your client connection see Client Network Connectivity and Troubleshooting the Client Connection.
Thales Data Protection on Demand (DPoD) will be changing the Identity Provider (IDP) used in the DPoD platform to Thales OneWelcome. This update enables the platform to provide modern authentication options as well as simplifying logins for users that manage multiple tenants on the platform.
For more information about this upcoming change and potential impacts to you please see the DPoD IDP Migration FAQ.
In the upcoming release of FW 3.0 for Luna Cloud HSM, CPv1 will be removed from FIPS firmware support as it is no longer compliant with 140-3. As this only affects FIPS mode, all affected users should use CPv4 or transition service to non-FIPS mode. If Luna Network HSM users want to clone to Luna Cloud HSM with a FIPS partition they will have to use Luna 7.8 or higher. See Universal Cloning for more information.
FW 2.0.5 has been released to all production environments. This release resolves the issue with restoring Luna Cloud HSM backups from a Luna USB Backup HSM.
The new firmware versions based on region and FIPS mode are as follows:
Added
The issue with restoring Luna Cloud HSM backups from a Luna USB Backup HSM has been rectified with FW 2.0.5.
An issue was found with the Luna Cloud HSM Support Tool version 1.0.0 where incorrect data was reported for datacentre connectivity in some cases.
This issue has been fixed with the Luna Cloud HSM Support Tool version 1.0.2.
Luna Cloud HSM Support Tool version 1.0.2 addresses the following bug:
FW 2.0.2 has been released to all production environments. This release resolves an issue that prevented cloning objects between two Luna Cloud HSM partitions when using the 10.5 client.
The new firmware versions based on region and FIPS mode are as follows:
FW 2.0.2 includes the following bug fixes:
Cloning keys between two Luna Cloud HSM partitions fails when using the 10.5 client. There are currently two possible workaround scenarios.
-> Workaround #1 - If there is a Luna SA7 (or any other separate device to use as an intermediary for the cloning) then clone to and from that device.
-> Workaround #2 - If there is no separate device then completely uninstall the 10.5 client and install the 10.4 client from scratch. For this option please raise a support ticket to the Thales Customer Support portal to request to join the 2 partitions together as the 10.4 client does not support dynamic partition loading.
