Overview: Identity and sessions
Identity and session concepts distinguish authentication evidence, account scope and permission decisions.
A user label names a claimed account; authentication establishes the accepted identity under the server's contract. Authorization then evaluates an operation, and a login session has its own continuing state. These concepts explain why a successful sign-in is useful evidence without being permission for every later request.
Media server authentication
Media-server authentication verifies credential evidence for a requested account, while user/device labels and later operation permissions have separate roles.Media server authorization
Media-server authorization evaluates whether an established user context may perform a specific operation on the requested resource under the applicable policy.Server user identity
Server user identity associates a local account with its state and policy within one server, separately from display labels, device identity and optional Connect linkage.Login sessions
A login session retains accepted account evidence for subsequent requests, with token scope, validity and revocation separate from application-window or playback-session state.