The signaling protocol does not take into consideration that the JWT token registered from either the client or the device will expire. The WebRTC session does not have a timeout, but in cases where the JWT token is used continuously check authorization for a stream that stream will timeout once the JWT token expires.
The current signaling protocol states that it is not required to keep the connection to the signaling server alive. I suggest that an option to keep the connection alive is added and that an updateToken command is added, which sends in an updated JWT token. This is not a required command, but would allow for more solutions to support the ONVIF protocol.
Alternatively a WebRTC datachannel could be defined to handle communication like Update OAuth token.
The signaling protocol does not take into consideration that the JWT token registered from either the client or the device will expire. The WebRTC session does not have a timeout, but in cases where the JWT token is used continuously check authorization for a stream that stream will timeout once the JWT token expires.
The current signaling protocol states that it is not required to keep the connection to the signaling server alive. I suggest that an option to keep the connection alive is added and that an updateToken command is added, which sends in an updated JWT token. This is not a required command, but would allow for more solutions to support the ONVIF protocol.
Alternatively a WebRTC datachannel could be defined to handle communication like Update OAuth token.