Pega CHAT Client to send authorisation token as socket header
As a part of requirement in UBS, when Pega CHAT client snippet obtains a connection with the server via websocket, system has to send some authorisation token to the server to identify the request. This token is to be passed as a dynamic header of the request for socket.io connection. After going through the code we have understood that this might require a change in the chat.js file. Please confirm us how we can achieve the change?
I have the document with me but this document doesn't address our requirement. This document talks about event handling from Pega. Our requirement is to customize the client snippet to include dynamic header containing authorization token to pass through socket during communication.
This will help to identify the client chatting with the CSR agent. The token is to identify Web ChatUser from client side
Hi Swarnendu Mukherjee, this is not straightforward and out of scope for the current product. I would recommend against making custom changes like this as it tends to make the upgrade path for a customer a lot more difficult and make maintenance a headache.
That said, if you want to set up some time to discuss the customer's requirements and how we can meet them I'm happy to talk. Feel free to find a time on my calendar - and include Brett as well.
Posted: 6 years ago
Posted: 22 Apr 2016 12:50 EDT
Swarnendu Mukherjee (SwarnenduM)