Helping a customer get authenticated chat set up, and stumbled across a gap in the documentation.
I think the sample code maybe covers it all but I feel like there could be some documentation along with it to make it less of a fishing expedition.
Is there something I missed?
Is the end user joining the chat
a) assumed to have already been authenticated on the website so we can pass the information along with some confidence
or
b) going to be authenticated in the handler in custom service?
Maybe it sounds dumb but it's less than clear at this stage unless we totally missed a document on the site.
The authentication part is left up to you. Typically, what we see is that a customer offers chat to customers who are already logged into their website and then want to pass information about the customer securely. In that case, it'd be option a).
I'm not sure how option b) would work. I suppose you could offer chat to customers and then once they elect to chat, ask them to authenticate first before they are able to proceed. Implementation wise though, it still feels like option a).