@microsoft/omnichannel-chat-sdk 2.0.0-main.307c235 → 2.0.0-main.3932063

package/README.md

@@ -22,7 +22,6 @@ Please make sure you have a chat widget configured before using this package or
 - [SDK Methods](#sdk-methods)
   - [Initialization](#initialization)
   - [Start Chat](#start-chat)
-  - [Authenticate Chat](#authenticate-chat)
   - [End Chat](#end-chat)
   - [Get Pre-Chat Survey](#get-pre-chat-survey)
   - [Get Live Chat Config](#get-live-chat-config)
@@ -135,7 +134,7 @@ The npm `latest` dist-tag can point to a `main` prerelease. Use the exact versio
 
 Regenerate the application lockfile after the update. Then run the application build and tests on Node.js 22.
 
-Version `2.0.0` adds progressive bot-message streaming, mid-conversation authentication, read receipts, and unread-message counts. Existing `onNewMessage` handlers continue to receive final streaming messages.
+Version `2.0.0` adds progressive bot-message streaming, read receipts, and unread-message counts. Existing `onNewMessage` handlers continue to receive final streaming messages.
 
 See the [2.0 migration guide](docs/MIGRATION_2.0.md) for the complete upgrade and validation procedure.
 
@@ -331,32 +330,6 @@ const optionalParams = {
 await chatSDK.startChat(optionalParams);
 ```
 
-### Authenticate Chat
-
-It authenticates an active unauthenticated conversation. Enable optional authenticated sign-in for the workstream before you use this method.
-
-Call `initialize()` and `startChat()` before `authenticateChat()`. The first argument can be a token or an asynchronous token provider.
-
-```ts
-await chatSDK.initialize();
-await chatSDK.startChat();
-
-await chatSDK.authenticateChat(async () => {
-    const response = await fetch("https://contoso.example/token");
-    if (!response.ok) {
-        throw new Error("Token request failed");
-    }
-
-    return response.text();
-}, {
-    refreshChatToken: true
-});
-```
-
-Set `refreshChatToken` to `true` when subsequent SDK calls must use a refreshed authenticated chat token.
-
-The method throws `InvalidConversation` when no conversation is active. It throws `MidConversationAuthFailure` when token resolution or authentication fails.
-
 ### End Chat
 
 It ends the current Omnichannel conversation.
@@ -503,7 +476,7 @@ chatSDK.onNewMessage((message) => {
 
 ### On Streaming Message
 
-It subscribes to progressive ACS bot-message updates. This API is available only for Live Chat version 2.
+It subscribes to progressive ACS bot-message updates.
 
 Enable streaming when you start the conversation. Then register the handler after `startChat()` completes.
 
@@ -531,7 +504,7 @@ await chatSDK.onStreamingMessage((message) => {
 
 `streamingMessageType` can be `start`, `informative`, `streaming`, or `final`. A final message also reaches existing `onNewMessage` handlers.
 
-Calling this method before `startChat()` throws `UninitializedConversation`. Calling it for another Live Chat version throws `UnsupportedLiveChatVersion`.
+Calling this method before `startChat()` throws `UninitializedConversation`. If the conversation does not use ACS, this method throws `UnsupportedLiveChatVersion`.
 
 ### On Typing Event
 
@@ -690,7 +663,7 @@ const agentAvailability = await chatSDK.getAgentAvailability();
 
 Logs a particular message (and all previous messages) as read by the user. Read indicators will appear for Contact Center Representatives and Admins in the Admin Center.
 
-Authenticated chat sends the receipt through Messaging Runtime. Unauthenticated chat sends it through ACS and requires Live Chat version 2.
+Authenticated chat sends the receipt through Messaging Runtime. Unauthenticated chat sends the receipt through ACS.
 
 ```ts
 await chatSDK.sendReadReceipt(messageId: string);

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@microsoft/omnichannel-chat-sdk",
-  "version": "2.0.0-main.307c235",
+  "version": "2.0.0-main.3932063",
   "description": "Microsoft Omnichannel Chat SDK",
   "files": [
     "lib/**/*"