search

camaraproject / WebRTC

Repository to describe, develop, document and test the WebRTC API family
Apache License 2.0
5 stars 8 forks source link

Why transactionId and clientId headers must be present on get session in OneToOneCall API #19

Closed BenjaminBusvel closed 3 months ago

BenjaminBusvel commented 10 months ago

Problem description Why transactionId and clientId headers must be present on get session in OneToOneCall API

Expected behavior These fields must be populated at the POST session and can be returned in the post response with a sessionId in UUID format returned. For the get session only the sessionId returned at creation must be necessary

pradeepachar-mavenir commented 9 months ago

The transactionId is to track each of the requests made by the client. The clientId is an encoded value which shall be generated by encoding specific information related to the device. This shall enable the server to authenticate each and every requests made from the device by decoding and comparing with the values saved.

TEF-RicardoSerr commented 3 months ago

Make sense to keep it as Pradeep was saying