accessTokenFactory alludes to obtaining a string to use in HTTP requests, but I also see it added to the initial request on wss (and, presumably, ws). ws/wss are not the same as http/https. They are different protocols. Could you please clarify in the documentation what is meant?
I also do not see accessTokenFactory be called in subsequent websocket interactions, so if a token does change, I do not see this function called again. In that regard, if you truly only meant http, then documentation would be correct in that case.
Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.
ID: de8cdc99-48bb-3266-05bb-eda98f59f2e2
Version Independent ID: 66d252c3-6300-7e28-9aa0-ef2ff66e7a76
accessTokenFactory
alludes to obtaining a string to use in HTTP requests, but I also see it added to the initial request on wss (and, presumably, ws). ws/wss are not the same as http/https. They are different protocols. Could you please clarify in the documentation what is meant?I also do not see
accessTokenFactory
be called in subsequent websocket interactions, so if a token does change, I do not see this function called again. In that regard, if you truly only meant http, then documentation would be correct in that case.Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.