RN/WebRTCMedia Service/100.0.050.0000 - Revision history

WikiSysop at 07:45, September 21, 2022

2022-09-21T07:45:47Z

WikiSysop at 07:30, September 21, 2022

2022-09-21T07:30:46Z

WikiSysop: Created page with "{{ComponentRN |ComponentId=0371606b-df5e-41e2-869d-2009e76b916e |JQL=project = "WebRTC Media Service" AND id = WRTCMS-1066 OR id = WRTCMS-1062 |DeploymentTypeId=ec194bf2-b79a-..."

2022-06-22T03:45:34Z

Created page with "{{ComponentRN |ComponentId=0371606b-df5e-41e2-869d-2009e76b916e |JQL=project = "WebRTC Media Service" AND id = WRTCMS-1066 OR id = WRTCMS-1062 |DeploymentTypeId=ec194bf2-b79a-..."

New page

{{ComponentRN
|ComponentId=0371606b-df5e-41e2-869d-2009e76b916e
|JQL=project = "WebRTC Media Service" AND id = WRTCMS-1066 OR id = WRTCMS-1062
|DeploymentTypeId=ec194bf2-b79a-436d-8ff6-eaff94d9f43a, 5439f1be-1868-4091-b058-1667389b6ce1
|ReleaseDate=2022-06-21
|Highlight=This release includes important fixes.
}}
{{Issue
|TicketNumber=WRTCMS-1066
|IssueCategoryId=5c483167-c133-4dc5-87c0-bd2719670bc1
|Content=Previously, WebRTC Service incorrectly handled next scenario:# WebRTC client sends sign_in request to the WebRTC Gateway# WebRTC Gateway starts authentication procedure on GAuth service# Client is disconnected from the WebRTC Gateway# Authentication process is finishedAs result, WebRTC Gateway created a stale session without corresponding HTTP client which could affect real agent’s sessions.Now WebRTC Service does not create a stale session in case of the provided scenario.
|LocalContent=WebRTC Media Service now avoids the creation of a stale session while authenticating a <tt>sign_in</tt> request from a client.

Previously, when WebRTC Media Service handled the scenario in the following way, it led to a situation where the WebRTC Gateway created a stale session without a HTTP client, affecting the active agent’s sessions.

#The WebRTC client sends a <tt>sign_in</tt> request to the WebRTC Gateway.
#The WebRTC Gateway starts the authentication procedure on GAuth service.
#The client is disconnected from the WebRTC Gateway and the authentication process is completed.
}}
{{Issue
|TicketNumber=WRTCMS-1062
|IssueCategoryId=5c483167-c133-4dc5-87c0-bd2719670bc1
|Content=Now, WebRTC JS library uses generic API path for all “/sign_in” requests and sends them to the proper endpoint.
|LocalContent=WebRTC JS library now uses a generic API path for all "<tt>/sign_in</tt>" requests and sends the requests to the appropriate endpoint.
}}

@@ Line 4: / Line 4: @@
 |DeploymentTypeId=ec194bf2-b79a-436d-8ff6-eaff94d9f43a, 5439f1be-1868-4091-b058-1667389b6ce1, 8b480b3c-2733-433a-9166-eab2c2d0663a
 |ReleaseDate=2022-06-21
-|PrivateEditionReleaseDate=2022-09-20
+|PrivateEditionReleaseDate=2022-09-16
 |Highlight=This release includes important fixes.
 }}

@@ Line 2: / Line 2: @@
 |ComponentId=0371606b-df5e-41e2-869d-2009e76b916e
 |JQL=project = "WebRTC Media Service" AND id = WRTCMS-1066 OR id = WRTCMS-1062
-|DeploymentTypeId=ec194bf2-b79a-436d-8ff6-eaff94d9f43a, 5439f1be-1868-4091-b058-1667389b6ce1
+|DeploymentTypeId=ec194bf2-b79a-436d-8ff6-eaff94d9f43a, 5439f1be-1868-4091-b058-1667389b6ce1, 8b480b3c-2733-433a-9166-eab2c2d0663a
 |ReleaseDate=2022-06-21
 |Highlight=This release includes important fixes.
 }}
 {{Issue
 |TicketNumber=WRTCMS-1066
-|IssueCategoryId=5c483167-c133-4dc5-87c0-bd2719670bc1
+|IssueCategoryId=a8930ebb-8e46-4ecd-993f-cdd2d61bc400
 |Content=Previously, WebRTC Service incorrectly handled next scenario:# WebRTC client sends sign_in request to the WebRTC Gateway# WebRTC Gateway starts authentication procedure on GAuth service# Client is disconnected from the WebRTC Gateway# Authentication process is finishedAs result, WebRTC Gateway created a stale session without corresponding HTTP client which could affect real agent’s sessions.Now WebRTC Service does not create a stale session in case of the provided scenario.
 |LocalContent=WebRTC Media Service now avoids the creation of a stale session while authenticating a <tt>sign_in</tt> request from a client.