Hello all, As part of the container move for 7.0 we have been contemplating removing our notion of distributed sessions, since that feature is not provided for us by the container. The breakdown of this change would be. pros: - no custom tokening mechanism required, which eliminates concerns over exposing the token value (in cache, between client and server, etc.) - we never distributed any state beyond the authentication with the session, so eliminating this feature removes any expectation of transparent client failover. cons: - cached values in a cluster that are at a session level would not be available at other cluster members since a re-authentication would occur at each member. This affects plans and cached values using the hasRole, env, user functions, etc. Any thoughts?