Secure Session Management

Secure Session Management (SSM) is used with DRM to add further protection. A maximum number of concurrent sessions is associated with an account to prevent abuse by account sharing.

SSM sets up a session on an SSM server each time a piece of content plays. A session expires after a short time, so it must be regularly renewed. When playback stops, the session is torn down (destroyed) to allow another session to be created. If it is not regularly renewed or torn down, the SSM server deems the session expired, the license is not renewed and the session count drops by one.

The CONNECT Player SDK handles SSM with SSP, so all that player integration requires is setting some additional configuration data. There are two provided methods for SSM integration, called V1 and V2.

With V1, the SSM setup is performed separately before the playback/retrieving license, and the SSM teardown performed when the playback stops. See SSM v1 .

With V2 and the latest SSP license server v2 API, the SSM setup will be performed during the license request and there is no SSM setup from the client. The session will be torn down when zapping or the Application can call SSM tear down if the user does not zap but there is the need to free the session to give to other devices. See SSM v2 .