ContactLoop

內部上手指南 · 請先登入

沒有密碼?請向管理員索取。

Ava 功能說明

Chromeless 內嵌與 SSO 深連結

🔗④ Chromeless Embed Mode + SSO 深連結(供 SW Manager 內嵌使用)

這不是使用者自己會點進去的一頁,而是被 SW Manager 的「Unified Activity」入口內嵌的底層機制(見 SW 登入後導覽 → Unified Activity)。CEO 直接提出的需求「用同一個 SSO 身分,從 CL Manager 直達 CL Messenger 對話紀錄」,已在 CL1 驗證通過,且經過至少一輪安全性修補,新人若要 debug Unified Activity 顯示異常,要懂這一段。This isn't a page a user browses to directly — it's the underlying mechanism embedded by SW Manager's "Unified Activity" entry (see SW post-login tour → Unified Activity). It delivers a CEO-driven requirement — "reach CL Messenger conversation history directly from CL Manager under the same SSO identity" — already verified on CL1 and hardened by at least one security fix. New hires debugging odd Unified Activity behavior need to understand this.

Chromeless embed ?embed=1
Ava 提供 ?embed=1 模式,只渲染 Conversations 主體(Filters、對話列表、訊息串+composer、Journey State),不含 Ava 自己的頂列與側欄;搭配 CSP frame-ancestors 允許 Manager 網域框入。曾出現「偶發退回完整 chrome」的間歇性 bug,根因是頁面首次 client render 時 router.query 為空、與 redux-persist rehydration 競速,已改為 fallback 讀 window.location.search 修復。Ava exposes a ?embed=1 mode that renders only the Conversations body (Filters, conversation list, message thread + composer, Journey State) — no Ava top bar or sidebar — paired with a CSP frame-ancestors allowing the Manager domain to frame it. An intermittent "falls back to full chrome" bug was traced to router.query being empty on first client render, racing redux-persist rehydration; fixed by falling back to window.location.search.
SSO 深連結 (冷啟動 / 已登入)
從 Manager 點「Open CL Messenger」或直接開 deep link,若 Ava 尚未登入,會透過 SSO 靜默完成登入並落在正確帳號的對話頁(而非 fallback 到帳號 1)。框內(iframe)點 SSO 登入原本會被 X-Frame-Options 擋下,已改用 popup 流程處理,並修掉 popup 被瀏覽器擋掉/使用者中途關閉時卡住 spinner 的死路。Clicking "Open CL Messenger" from Manager or opening a deep link directly, when Ava isn't logged in yet, silently completes SSO and lands on the correct account's conversation page (not a fallback to account 1). Clicking SSO login inside the iframe used to be blocked by X-Frame-Options; it's now routed through a popup flow, with fixes for the popup being blocked by the browser or closed mid-flow leaving the UI stuck on a spinner.
安全性修補(LT623)
embed 身分驗證改為 fail closed(驗證失敗就不顯示內容,不是放行);內嵌 Conversations 面板改為綁定 host 端(Manager)登入者身分,避免權限外洩(修前可能出現「iframe 裡看到的資料權限跟 Manager 登入者對不上」的漏洞)。Embed identity verification was changed to fail closed (verification failure hides content instead of allowing it through); the embedded Conversations panel is now bound to the host-side (Manager) logged-in identity, closing a permission-leak gap where the iframe's data access could previously diverge from the Manager-side identity.
已知功能缺口(非 bug)
若一個 SW 帳號歷史上對應到不只一個 Ava App Integration,Unified Activity 目前只自動解析第一個 enabled 的整合,無法從此頁切換查看其他整合——這是 AC 明訂的刻意行為(1:1 情境下不做手動下拉選單),已開獨立 follow-up 卡追蹤產品面決策,不是 regression。If a SW account historically maps to more than one Ava App Integration, Unified Activity currently only auto-resolves the first enabled integration — there's no way to switch to the others from this page. This is deliberate per the AC (no manual dropdown in the 1:1 case), tracked by a separate follow-up card for a product decision — not a regression.