...

When RTSP connection is established, /playRTSP query will be sent to backend server application defaultApp

URL:http://localhost:8081/apps/EchoApp/playRTSP
OBJECT:
{
  "nodeId" : "NTk1tLorQ00llGbPJuFexrKceubGCR0k@192.168.1.5",
  "appKey" : "defaultApp",
  "sessionId" : "/192.168.1.100:59711/192.168.1.5:554",
  "mediaSessionId" : "29868390-73ee-4f49-ba92-78d717c53070-test-RTSP",
  "name" : "rtsp://p11.flashphoner.com:554/test",
  "mediaProvider" : "RTSP",
  "userAgent" : "LibVLC/3.0.4 (LIVE555 Streaming Media v2016.11.28)"
}

...

Thus, RTSP client can be authenticated by RTSP stream URL, User-Agent, client and server IP address and port.

Custom access key and backend application usage for RTSP playback authentication

Since build 5.2.1008 it is possible to set ccustom authentication key (token) in RTSP URL, for example

rtsp://wcs:5554/streamName?aclAuth=1254789

The following REST hook /playRTSP content will be sent to defaultApp backend application

{
  "nodeId" : "XLepaP08Uyz9LqAjXHWnwuFxrEri0fCj@192.168.1.39",
  "appKey" : "testApp",
  "sessionId" : "/192.168.1.83:55195/192.168.1.39:5554",
  "mediaSessionId" : "71317dfc-0222-4acd-912e-57e67f2a272a-streamName-RTSP",
  "name" : "rtsp://wcs:5554/streamName?aclAuth=1254789",
  ...
  "mediaProvider" : "RTSP",
  "userAgent" : "LibVLC/3.0.8 (LIVE555 Streaming Media v2016.11.28)",
  "custom" : {
    "aclAuth" : "1254789"
  }
}

Authentication token name is set by the following parameter as like for HLS playback

client_acl_property_name=aclAuth

It is also possible to set custom backend application key

rtsp://wcs:5554/streamName?appKey=customAppKey&aclAuth=1254789

In this case REST hook /playHLS will be sent to backend application with defined key (customAppKey in the example above).

Adjusting RTSP playback parameters

...