# Ripple Custody 1.15 (September 27, 2024)

Version 1.15 is a SaaS and on-premise release and introduces the following new features:

- User experience
  - [Single sign-on](#single-sign-on-sso)
- Key management
  - [AWS CloudHSM](#aws-cloudhsm)
- Custody
  - [Transaction block date](#transaction-block-date)
  - [Scam token screening](#scam-token-screening)
- [Breaking changes](#breaking-changes)


For on-premise customers, version 1.15 also includes the features of the following SaaS versions:

- [Ripple Custody 1.14](/products/custody/v1.19/support/change-history/v114)
- [Ripple Custody 1.13](/products/custody/v1.19/support/change-history/v113)


For information about distribution and deployment of this version, see [Distribution and deployment](#distribution-and-deployment).

## Single sign-on (SSO)

Our whole customer base can now benefit from increased flexibility when logging in to the Ripple Custody UI, with, in addition to the default internal OIDC login provided as standard, the possibility to integrate your own OAuth and OIDC external identity providers with the Ripple Custody UI.

For more information, see [Register and log in](/products/custody/v1.19/ui/get-started/register) in the Ripple Custody UI guide.

## AWS CloudHSM

Ripple Custody has expanded its wallet and key management capabilities to include official support for AWS CloudHSM. You can now deploy Ripple Custody vaults to AWS and seamlessly connect to these single-tenant hardware security modules on AWS Cloud, supporting strong security practices while enabling scalable, low-latency cryptographic operations integrated with other AWS services.

## Transaction block date

We have introduced a new field to report the date of block creation on the ledger in our transactions. The benefits of this field are as follows:

- Regulatory compliance: Meets the stringent requirements for capital market transactions.
- Increased transparency: Provides a clearer distinction between different transaction timestamps.


For examples of the new `ledgerTransactionData.blockTime` field, see the following 200 responses:

- [List transactions](/products/custody/v1.19/api/reference/openapi/transactions/gettransactions)
- [Get transaction details](/products/custody/v1.19/api/reference/openapi/transactions/gettransaction)


## Scam token screening

This release introduces enhanced fraud protection, in the form of scam token screening.
All new accounts benefit from an increased level of protection by tracking only transactions and balances of native currencies during account creation.

In on-premise environments, this feature is not enabled by default. To request it, open a new ticket in our Support portal.

## Breaking changes

The SSO feature requires that all user entries be migrated to a new format. You must complete this migration before you can use 1.15 and all future versions of the product.

Once migration is completed, the URL of the authentication endpoint changes, as follows:

- Old URL format: `https://auth.<HOST_URL>/token`
- New URL format: `https://openid.<HOST_URL>/realms/Metaco/protocol/openid-connect/token`


For more information, see the [Migration guide](/products/custody/v1.19/get-started/deployment/migration-guide).

## Distribution and deployment

Before you upgrade to 1.15, note the breaking change described in [Breaking changes](#breaking-changes).

### Ripple Cloud

The upgrade will be done progressively starting on September 30, 2024 across the various environments. The production environment will be upgraded last, with a deployment planned on October 14, 2024. This may be delayed, based on customer feedback.

### On-premise

Version 1.15 will be available for our on-premise customers to download and install from September 27, 2024. You can pull the containers from Ripple’s repository using the `1.15.0` tag. On-premise version 1.15 also includes all the cumulative updates of SaaS versions 1.14 and 1.13.

As with all new releases, this version triggers the deprecation of the previous version (v1.12.x), which will continue to be supported for the next 6 months, unless specified otherwise in the master contract with Ripple. For more information about versioning, see [Versioning and release management](/products/custody/v1.19/support/release-management).

To ensure you stay up-to-date with the latest API deprecations and changes, end of support for previous versions, and how your operating model might be affected, remember to regularly check the [Release history](/products/custody/v1.19/support/change-history#release-history) and [API deprecations and changes](/products/custody/v1.19/support/change-history#api-deprecations-and-changes).

### Activation and support

The configuration of new functionalities can sometimes present technical challenges and require the support of our team. If you need any technical assistance, contact your Ripple liaison.