Users and Playback Access
Users authenticate playback. Give each User either a reusable Package or a custom access policy before distributing playlists or playback URLs.
Main Actions
| Action | When to Use | How to Use |
|---|---|---|
| Manage Users | Check expiration, connections, effective access, or credentials. | Open User → Manage Users, find the User, then review its effective summary before editing. |
| Add User | Create playback access. | Open User → Add User, choose authentication, expiration, limits, and Package or custom access, then save and test it. |
Create Playback Access
- Put the required Streams and VOD in Bouquets.
- Create a Package with Bouquets, duration, connection limit, resolution limit, and CDN servers.
- Add the User and select that Package, or configure a one-off custom policy.
- Review the effective User summary.
- Test authorized and unauthorized media with the User’s real credentials.
Categories organize content for administrators. Bouquets decide which content a Package or custom User may play.
Authentication
| Mode | Use When |
|---|---|
| Password | The client can send a unique username and password over HTTPS |
| IP | The viewer has a stable, trusted address without carrier NAT or frequent changes |
Usernames and passwords are 6–32 characters in the current UI. Never reuse administrator credentials or API tokens. Configure trusted proxies carefully so clients cannot spoof forwarded addresses.
Package or Custom Access
Use a Package when multiple Users share the same duration, Bouquets, connection limit, resolution limit, and CDN policy. Use Custom only for one User exception.
Live HLS, DASH, HTTP-TS, and RTMP respect the resolution limit. ABR manifests include only variants at or below the permitted height. Confirm how the current UI interprets a zero connection value instead of assuming it means unlimited.
Playback and Connections
Use URLs generated by Engine; do not construct undocumented paths. Test playlist refresh, HLS/DASH selection, long-lived HTTP-TS, VOD seeking and Range requests, expiration, unauthorized media, and reconnection at the connection limit.
Engine enforces the User/Package limit and the selected server’s licensed connection limit separately. Use System → Connections to inspect or kick sessions. Before increasing limits, check shared credentials, reconnect loops, stale clients, and CDN selection.
Playlist and EPG
Open User → Manage Users and select Playlist for the intended User.
- Select HLS, HTTP-TS, or RTMP. Media without that output is omitted.
- Select the M3U attributes to include: TVG-ID, TVG-NAME, TVG-LOGO, and GROUP TITLE.
- Copy or download the generated Playlist URL and EPG URL.
- Open Player and test with the same User authentication.
Password-authenticated links include the User credentials. Treat generated URLs as secrets and use HTTPS. IP-authenticated Users rely on the client address seen by Engine, so verify trusted-proxy settings before distribution.
Warning
Test as the User: Administrator preview does not prove customer authorization. Test the exact User, Package, protocol, TLS path, and CDN route used in production.