Closed pikachu937 closed 1 year ago
try to build a new mediamtx binary with this commit https://github.com/bluenviron/mediamtx/commit/2faca7374942aef79ff94bbfb3e578bf6bbb2817 included or wait for v0.23.7 to try again
try to build a new mediamtx binary with this commit 2faca73 included or wait for v0.23.7 to try again
I checked yesterday with a different(more recent) commit 972cd58 which already includes the 2faca73 commit you suggested, no change.
"path":"path1","protocol":"webrtc","id":null,"action":"read","query":""
Commit 2faca73 is unrelated from this issue, that will be solved soon.
This is fixed by #2098. Keep in my that you will still see requests with an empty ID because browser-based WebRTC clients send two anonymous requests to the server before starting a session:
Regarding external authentication, my advice is to use a fixed string that expires after some time, like a JWT.
This issue is being locked automatically because it has been closed for more than 6 months. Please open a new issue in case you encounter a similar problem.
Which version are you using?
v0.23.6
Which operating system are you using?
Describe the issue
empty id when using external authentication for webrtc
Describe how to replicate the issue
Example: {"ip":"192.168.0.1","user":"test","password":"test123","path":"path1","protocol":"webrtc","id":null,"action":"read","query":""} [|http]
but if i read rtsp link, param id set correctly Example: {"ip":"192.168.0.1","user":"test","password":"test123","path":"path1","protocol":"rtsp","id":"09872164-0b5b-47db-886e-816d40222a74","action":"publish","query":""} [|http]
Did you attach the server logs?
yes / no
Did you attach a network dump?
yes / no