Will the default DataSealer stay replaceable?

[Cantor, Scott]

> Is there a better/more correct solution for our issue? 

You would need to switch all of ther relevant components to use alternate StorageService-based implementations (but that's not going to cluster using the in-memory variant).

If you're trying to implement something for replication of data, it's the StorageService interface you have to implement to, not the DataSealer, and other properties requiring an override.

There are a many aspects of the IdP [1] that have to get pointed to an alternative, not just the token encoding mechanism, and most of them use the ClientStorageService bean, which uses the DataSealer, it's not the DataSealer itself.

-- Scott

[1] Sessions, replay cache, transient IDs in certain cases, the OP's many use cases, I'm sure others I'm not thinking of.