You can add Field Carry-Over

Use these options to enable the security controls and fields you want carried over from the access token into the session token. These allow for better access control and analysis.

Review the information in the table that follows to determine if including a field benefits your delivery.

Field Description Benefit/Drawback
Session-Id (Enabled by default) Enable this to carry-over the session_id from the access token to the session token.

This allows for tracking and counting unique playback sessions for a URL that is protected by a session token.

Note: This needs to remain enabled if you want to use Access Revocation.
Data/Payload Once enabled, information is carried over from the data/payload field in the access token to the session token.

This allows access to opaque data for log analysis for a URL that is protected by a session token.

IP Once enabled, the ip field is carried over from the access token to the session token. This limits access to requesting client access to the specific ip address included in the token.

Only enable this if the IP address used by the player will not change during the playback session.

For example, if you're working with mobile clients, they may switch from Wi-Fi to cellular (or vice versa), so the IP address for that device would vary during playback. So, you probably wouldn't want to enable this field for carry-over.

ACL Once enabled, the acl field is carried over from the access token to the session token. This limits requesting client access to the specific URL or path set in the acl field.

Only enable this if the base path for the master playlist—and the variant/bitrate playlists and segments—are the same. Playback can fail if this is not the case.