[{"data":1,"prerenderedAt":3226},["ShallowReactive",2],{"i-lucide:globe":3,"i-lucide:menu":8,"i-lucide:newspaper":10,"i-lucide:box":12,"i-lucide:chevron-down":14,"i-lucide:layout-grid":16,"i-lucide:pen-line":18,"i-lucide:book-open":20,"i-lucide:linkedin":22,"i-lucide:facebook":25,"i-lucide:youtube":27,"i-lucide:arrow-up":29,"manual-tw-orphelink\u002Forphelink-setting\u002Fauth-connect":31,"manual-navigation-tw":2809,"i-lucide:panel-left":3216,"i-lucide:search":3218,"i-lucide:chevron-right":3220,"i-lucide:arrow-left":3222,"i-lucide:arrow-right":3224},{"left":4,"top":4,"width":5,"height":5,"rotate":4,"vFlip":6,"hFlip":6,"body":7},0,24,false,"\u003Cg fill=\"none\" stroke=\"currentColor\" stroke-linecap=\"round\" stroke-linejoin=\"round\" stroke-width=\"2\">\u003Ccircle cx=\"12\" cy=\"12\" r=\"10\"\u002F>\u003Cpath d=\"M12 2a14.5 14.5 0 0 0 0 20a14.5 14.5 0 0 0 0-20M2 12h20\"\u002F>\u003C\u002Fg>",{"left":4,"top":4,"width":5,"height":5,"rotate":4,"vFlip":6,"hFlip":6,"body":9},"\u003Cpath fill=\"none\" stroke=\"currentColor\" stroke-linecap=\"round\" stroke-linejoin=\"round\" stroke-width=\"2\" d=\"M4 5h16M4 12h16M4 19h16\"\u002F>",{"left":4,"top":4,"width":5,"height":5,"rotate":4,"vFlip":6,"hFlip":6,"body":11},"\u003Cg fill=\"none\" stroke=\"currentColor\" stroke-linecap=\"round\" stroke-linejoin=\"round\" stroke-width=\"2\">\u003Cpath d=\"M15 18h-5m8-4h-8m-6 8h16a2 2 0 0 0 2-2V4a2 2 0 0 0-2-2H8a2 2 0 0 0-2 2v16a2 2 0 0 1-4 0v-9a2 2 0 0 1 2-2h2\"\u002F>\u003Crect width=\"8\" height=\"4\" x=\"10\" y=\"6\" rx=\"1\"\u002F>\u003C\u002Fg>",{"left":4,"top":4,"width":5,"height":5,"rotate":4,"vFlip":6,"hFlip":6,"body":13},"\u003Cg fill=\"none\" stroke=\"currentColor\" stroke-linecap=\"round\" stroke-linejoin=\"round\" stroke-width=\"2\">\u003Cpath d=\"M21 8a2 2 0 0 0-1-1.73l-7-4a2 2 0 0 0-2 0l-7 4A2 2 0 0 0 3 8v8a2 2 0 0 0 1 1.73l7 4a2 2 0 0 0 2 0l7-4A2 2 0 0 0 21 16Z\"\u002F>\u003Cpath d=\"m3.3 7l8.7 5l8.7-5M12 22V12\"\u002F>\u003C\u002Fg>",{"left":4,"top":4,"width":5,"height":5,"rotate":4,"vFlip":6,"hFlip":6,"body":15},"\u003Cpath fill=\"none\" stroke=\"currentColor\" stroke-linecap=\"round\" stroke-linejoin=\"round\" stroke-width=\"2\" d=\"m6 9l6 6l6-6\"\u002F>",{"left":4,"top":4,"width":5,"height":5,"rotate":4,"vFlip":6,"hFlip":6,"body":17},"\u003Cg fill=\"none\" stroke=\"currentColor\" stroke-linecap=\"round\" stroke-linejoin=\"round\" stroke-width=\"2\">\u003Crect width=\"7\" height=\"7\" x=\"3\" y=\"3\" rx=\"1\"\u002F>\u003Crect width=\"7\" height=\"7\" x=\"14\" y=\"3\" rx=\"1\"\u002F>\u003Crect width=\"7\" height=\"7\" x=\"14\" y=\"14\" rx=\"1\"\u002F>\u003Crect width=\"7\" height=\"7\" x=\"3\" y=\"14\" rx=\"1\"\u002F>\u003C\u002Fg>",{"left":4,"top":4,"width":5,"height":5,"rotate":4,"vFlip":6,"hFlip":6,"body":19},"\u003Cpath fill=\"none\" stroke=\"currentColor\" stroke-linecap=\"round\" stroke-linejoin=\"round\" stroke-width=\"2\" d=\"M13 21h8m.174-14.188a1 1 0 0 0-3.986-3.987L3.842 16.174a2 2 0 0 0-.5.83l-1.321 4.352a.5.5 0 0 0 .623.622l4.353-1.32a2 2 0 0 0 .83-.497z\"\u002F>",{"left":4,"top":4,"width":5,"height":5,"rotate":4,"vFlip":6,"hFlip":6,"body":21},"\u003Cpath fill=\"none\" stroke=\"currentColor\" stroke-linecap=\"round\" stroke-linejoin=\"round\" stroke-width=\"2\" d=\"M12 7v14m-9-3a1 1 0 0 1-1-1V4a1 1 0 0 1 1-1h5a4 4 0 0 1 4 4a4 4 0 0 1 4-4h5a1 1 0 0 1 1 1v13a1 1 0 0 1-1 1h-6a3 3 0 0 0-3 3a3 3 0 0 0-3-3z\"\u002F>",{"left":4,"top":4,"width":5,"height":5,"rotate":4,"vFlip":6,"hFlip":6,"body":23,"hidden":24},"\u003Cg fill=\"none\" stroke=\"currentColor\" stroke-linecap=\"round\" stroke-linejoin=\"round\" stroke-width=\"2\">\u003Cpath d=\"M16 8a6 6 0 0 1 6 6v7h-4v-7a2 2 0 0 0-2-2a2 2 0 0 0-2 2v7h-4v-7a6 6 0 0 1 6-6M2 9h4v12H2z\"\u002F>\u003Ccircle cx=\"4\" cy=\"4\" r=\"2\"\u002F>\u003C\u002Fg>",true,{"left":4,"top":4,"width":5,"height":5,"rotate":4,"vFlip":6,"hFlip":6,"body":26,"hidden":24},"\u003Cpath fill=\"none\" stroke=\"currentColor\" stroke-linecap=\"round\" stroke-linejoin=\"round\" stroke-width=\"2\" d=\"M18 2h-3a5 5 0 0 0-5 5v3H7v4h3v8h4v-8h3l1-4h-4V7a1 1 0 0 1 1-1h3z\"\u002F>",{"left":4,"top":4,"width":5,"height":5,"rotate":4,"vFlip":6,"hFlip":6,"body":28,"hidden":24},"\u003Cg fill=\"none\" stroke=\"currentColor\" stroke-linecap=\"round\" stroke-linejoin=\"round\" stroke-width=\"2\">\u003Cpath d=\"M2.5 17a24.1 24.1 0 0 1 0-10a2 2 0 0 1 1.4-1.4a49.6 49.6 0 0 1 16.2 0A2 2 0 0 1 21.5 7a24.1 24.1 0 0 1 0 10a2 2 0 0 1-1.4 1.4a49.6 49.6 0 0 1-16.2 0A2 2 0 0 1 2.5 17\"\u002F>\u003Cpath d=\"m10 15l5-3l-5-3z\"\u002F>\u003C\u002Fg>",{"left":4,"top":4,"width":5,"height":5,"rotate":4,"vFlip":6,"hFlip":6,"body":30},"\u003Cpath fill=\"none\" stroke=\"currentColor\" stroke-linecap=\"round\" stroke-linejoin=\"round\" stroke-width=\"2\" d=\"m5 12l7-7l7 7m-7 7V5\"\u002F>",{"id":32,"title":33,"body":34,"depth":1898,"description":2794,"extension":2795,"locale":2796,"meta":2797,"navigation":24,"order":2798,"parent_path":2799,"path":2800,"path_key":2801,"product":2802,"product_order":4,"search_text":2803,"seo":2804,"sidebar":24,"source_locale":2805,"stem":2806,"version":2807,"visible":24,"__hash__":2808},"manual\u002Fmanual\u002Ftw\u002Forphelink\u002Forphelink-setting\u002Fauth-connect.md","Auth Connect",{"type":35,"value":36,"toc":2757},"minimark",[37,41,57,71,75,78,195,204,207,211,222,226,229,232,288,291,294,297,346,349,352,371,376,380,465,469,475,559,566,570,651,654,657,666,670,700,746,751,755,759,777,783,842,847,851,854,859,930,936,951,955,1026,1032,1044,1048,1051,1105,1108,1157,1163,1168,1185,1188,1228,1234,1284,1289,1292,1326,1332,1337,1340,1368,1374,1383,1386,1414,1420,1427,1493,1501,1504,1520,1526,1531,1535,1538,1587,1619,1625,1630,1634,1638,1672,1678,1683,1687,1746,1752,1760,1765,1791,1794,1805,1809,1866,1870,1873,1878,1884,1890,1896,1918,1924,1936,1941,1945,1993,1997,2000,2034,2040,2046,2050,2059,2099,2105,2114,2117,2128,2134,2137,2154,2160,2165,2169,2176,2200,2206,2230,2236,2242,2248,2253,2265,2269,2331,2341,2347,2358,2362,2369,2382,2400,2405,2412,2426,2432,2445,2452,2476,2482,2497,2505,2513,2532,2536,2539,2572,2578,2583,2587,2590,2604,2730,2736,2740],[38,39,33],"h2",{"id":40},"auth-connect",[42,43,44,48,49,52,53,56],"p",{},[45,46,47],"strong",{},"OrpheLink Auth Connect"," 是 Data Plane 的使用者身分驗證機制。整合 ",[45,50,51],{},"Local \u002F AD \u002F RADIUS 身分來源","與 ",[45,54,55],{},"TOTP MFA 雙重驗證","，結合精確的設備授權規則，確保只有通過核准的使用者能存取指定設備。使用者可透過 OrpheAgent 桌面 GUI 或網頁 Captive Portal 快速完成登入。",[58,59,60],"blockquote",{},[42,61,62,63,66,67,70],{},"設備連上網路之後，再確認「",[45,64,65],{},"正確的人","」只能存取「",[45,68,69],{},"被授權的設備","」。\n支援 Local Account、Active Directory（AD）、RADIUS，以及 TOTP 多因素驗證（MFA）。",[38,72,74],{"id":73},"快速開始5-步完成-auth-connect","快速開始：5 步完成 Auth Connect",[42,76,77],{},"先看這一頁，了解整體流程；每一步的細節在後面的章節。",[79,80,81,100],"table",{},[82,83,84],"thead",{},[85,86,87,91,94,97],"tr",{},[88,89,90],"th",{},"步驟",[88,92,93],{},"誰做",[88,95,96],{},"做什麼",[88,98,99],{},"完成的樣子",[101,102,103,126,143,164,182],"tbody",{},[85,104,105,109,112,123],{},[106,107,108],"td",{},"1",[106,110,111],{},"管理員",[106,113,114,115,118,119,122],{},"決定登入來源（Local／AD／RADIUS）。使用 AD 或 RADIUS 時，先在 ",[45,116,117],{},"AD settings","／",[45,120,121],{},"RADIUS settings"," 完成串接並測試",[106,124,125],{},"測試結果通過，按 Apply 儲存",[85,127,128,131,133,140],{},[106,129,130],{},"2",[106,132,111],{},[106,134,135,136,139],{},"在 Auth Connect 按 ",[45,137,138],{},"Add"," 建立規則，指定來源、可存取的設備（Authorized Devices）與 MFA Policy",[106,141,142],{},"規則出現在清單，Toggle 為 Enable",[85,144,145,148,150,157],{},[106,146,147],{},"3",[106,149,111],{},[106,151,152,153,156],{},"到目標節點開啟 ",[45,154,155],{},"Authentication","，選擇要套用的規則",[106,158,159,160,163],{},"節點收到設定（",[45,161,162],{},"沒做這步，規則不會生效","）",[85,165,166,169,172,179],{},[106,167,168],{},"4",[106,170,171],{},"使用者",[106,173,174,175,178],{},"在 OrpheAgent 的 ",[45,176,177],{},"Data Plane Auth","（或瀏覽器 Captive Portal）輸入帳號密碼；需要 MFA 時再輸入 6 位動態碼",[106,180,181],{},"可以連到被授權的設備",[85,183,184,187,189,192],{},[106,185,186],{},"5",[106,188,111],{},[106,190,191],{},"驗收：未登入時被擋、登入後放行、未授權的設備仍被擋",[106,193,194],{},"三項結果都符合預期",[58,196,197],{},[42,198,199,200,203],{},"⚠️ ",[45,201,202],{},"最常見的錯誤："," 建立了規則，卻忘記在目標節點開啟 Authentication。這種情況下流量不會被攔截，也不會要求登入。",[205,206],"hr",{},[38,208,210],{"id":209},"一功能說明","一、功能說明",[42,212,213,214,217,218,221],{},"Auth Connect 是 OrpheLink 對 OrpheAgent 資料平面（Data Plane）的",[45,215,216],{},"使用者身分驗證","與",[45,219,220],{},"設備存取授權","功能。管理員建立登入規則，使用者通過驗證後，才能存取規則允許的設備。",[223,224,225],"h3",{"id":225},"為什麼需要它",[42,227,228],{},"設備顯示 Online，只代表加密通道建立了，不代表「現在坐在電腦前的人」有權使用。Auth Connect 在封包抵達受保護節點之前，要求使用者先證明身分與存取權限。",[223,230,231],{"id":231},"三大防線中的位置",[79,233,234,247],{},[82,235,236],{},[85,237,238,241,244],{},[88,239,240],{},"防線",[88,242,243],{},"要回答的問題",[88,245,246],{},"驗證方式",[101,248,249,260,277],{},[85,250,251,254,257],{},[106,252,253],{},"第一道：設備認證（Device Auth）",[106,255,256],{},"哪台設備可以開通 Data Plane 加入網路？",[106,258,259],{},"指定 Email ＋ Magic Link 核准",[85,261,262,267,272],{},[106,263,264],{},[45,265,266],{},"第二道：身分連線認證（Auth Connect）",[106,268,269],{},[45,270,271],{},"誰正在使用這台設備存取目標資源？",[106,273,274],{},[45,275,276],{},"企業帳密（Local／AD／RADIUS）＋ TOTP MFA",[85,278,279,282,285],{},[106,280,281],{},"第三道：服務白名單（Service White List）",[106,283,284],{},"這台設備只能連到對方的哪些 Port？",[106,286,287],{},"TCP\u002FUDP ＋ Port ＋ 允許的 Neighbor 範圍",[42,289,290],{},"Auth Connect 不會取代設備核准或防火牆規則，三者各自獨立驗證。",[223,292,293],{"id":293},"三個核心關卡",[42,295,296],{},"封包只有依序通過以下三關，才會被轉送：",[79,298,299,311],{},[82,300,301],{},[85,302,303,306,308],{},[88,304,305],{},"關卡",[88,307,243],{},[88,309,310],{},"管理員在哪裡設定",[101,312,313,324,335],{},[85,314,315,318,321],{},[106,316,317],{},"身分來源（Auth source）",[106,319,320],{},"你是誰？",[106,322,323],{},"Add 規則時選擇；AD、RADIUS 另需串接設定",[85,325,326,329,332],{},[106,327,328],{},"設備授權（Authorized Devices）",[106,330,331],{},"你能去哪？",[106,333,334],{},"每條規則的 Devices／Authorized Devices",[85,336,337,340,343],{},[106,338,339],{},"MFA 政策（MFA Policy）",[106,341,342],{},"要不要多一道鎖？",[106,344,345],{},"MFA Settings 與每條規則的 MFA Policy",[223,347,348],{"id":348},"一個辦公室故事",[42,350,351],{},"公司有「辦公室檔案伺服器」與「研發測試機」。小明是一般員工，只能連檔案伺服器；小華是 IT 人員，可以連兩台，而且重要設備必須輸入手機驗證碼。",[353,354,355,359,362,365,368],"ol",{},[356,357,358],"li",{},"IT 管理員為小明、小華建立登入規則。",[356,360,361],{},"管理員決定每條規則允許的設備：小明只有檔案伺服器。",[356,363,364],{},"管理員為重要設備設定 MFA Required，並確認目標設備已開啟 Authentication。",[356,366,367],{},"員工在 OrpheAgent 選擇目標設備並登入，必要時完成手機驗證碼。",[356,369,370],{},"通過後才能連線到被允許的設備；不在清單內的設備仍會被拒絕。",[58,372,373],{},[42,374,375],{},"ℹ️ 這裡的「登入成功」指的是資料面的存取授權，不代表能登入 OrpheLink 管理後台，也不代表對方設備本身的檔案權限全部開放。",[38,377,379],{"id":378},"二名詞白話對照","二、名詞白話對照",[79,381,382,392],{},[82,383,384],{},[85,385,386,389],{},[88,387,388],{},"介面上的字",[88,390,391],{},"白話說明",[101,393,394,401,409,417,425,433,441,449,457],{},[85,395,396,398],{},[106,397,33],{},[106,399,400],{},"管理「誰能用什麼方式登入、能連到哪些設備」的規則",[85,402,403,406],{},[106,404,405],{},"OrpheLink",[106,407,408],{},"管理員設定規則的控制中心",[85,410,411,414],{},[106,412,413],{},"OrpheAgent／Node／Neighbor",[106,415,416],{},"電腦上的連線程式／被管理的設備／清單中的另一台設備",[85,418,419,422],{},[106,420,421],{},"Auth source",[106,423,424],{},"帳號密碼從哪裡驗證，例如 OrpheLink 自建、公司 AD、公司 RADIUS",[85,426,427,430],{},[106,428,429],{},"Authorized Devices",[106,431,432],{},"這條規則通過驗證後，可存取的目標設備範圍",[85,434,435,438],{},[106,436,437],{},"MFA／TOTP",[106,439,440],{},"密碼之外，再用手機驗證器產生的 6 位數動態碼（每 30 秒更新）",[85,442,443,446],{},[106,444,445],{},"Recovery Code",[106,447,448],{},"手機無法產生驗證碼時使用的一次性備用碼",[85,450,451,454],{},[106,452,453],{},"Session／Timeout",[106,455,456],{},"驗證通過後暫時有效的存取狀態，與其逾時時間",[85,458,459,462],{},[106,460,461],{},"Captive Portal",[106,463,464],{},"因存取受保護網頁而跳出的瀏覽器登入畫面",[38,466,468],{"id":467},"三身分來源選擇登入方式","三、身分來源：選擇登入方式",[42,470,471,472,474],{},"新增規則時，管理員在 ",[45,473,421],{}," 選擇帳號來源。使用者仍用熟悉的帳號密碼登入，不必改變習慣。",[79,476,477,489],{},[82,478,479],{},[85,480,481,483,486],{},[88,482,421],{},[88,484,485],{},"驗證與授權方式",[88,487,488],{},"使用者登入時輸入",[101,490,491,502,513,523,538,549],{},[85,492,493,496,499],{},[106,494,495],{},"Local Account",[106,497,498],{},"帳號與密碼由 OrpheLink 規則管理",[106,500,501],{},"管理員建立的 Account Name 與密碼",[85,503,504,507,510],{},[106,505,506],{},"AD Group",[106,508,509],{},"AD 使用者須屬於指定的 Security Group，並通過個人密碼驗證",[106,511,512],{},"完整 UPN 與 AD 密碼",[85,514,515,518,521],{},[106,516,517],{},"All AD Users",[106,519,520],{},"所有符合 Directory 與規則設備範圍的 AD 使用者",[106,522,512],{},[85,524,525,528,535],{},[106,526,527],{},"RADIUS - User",[106,529,530,531],{},"指定單一完整的 ",[532,533,534],"code",{},"username@realm",[106,536,537],{},"該帳號的 RADIUS 密碼",[85,539,540,543,546],{},[106,541,542],{},"RADIUS - Policy (Filter-Id)",[106,544,545],{},"僅允許 Access-Accept 回覆中帶有指定完整 Filter-Id 的使用者",[106,547,548],{},"RADIUS 帳號與密碼",[85,550,551,554,557],{},[106,552,553],{},"RADIUS - All Users",[106,555,556],{},"符合 Realm 與設備範圍的 RADIUS 使用者都可嘗試驗證",[106,558,548],{},[42,560,561],{},[562,563],"img",{"alt":564,"src":565},"圖 1｜新增規則時的 Auth source 選單：Local、AD 與三種 RADIUS 規則","\u002Fimages\u002Fmanual\u002Forphelink\u002Forphelink-setting\u002Fauth-connect\u002Fimage-01.webp",[223,567,569],{"id":568},"該選哪一種","該選哪一種？",[79,571,572,585],{},[82,573,574],{},[85,575,576,579,582],{},[88,577,578],{},"公司情境（示例）",[88,580,581],{},"適合的 Auth source",[88,583,584],{},"原因",[101,586,587,597,607,617,627,641],{},[85,588,589,592,594],{},[106,590,591],{},"訪客或測試人員需要一組暫時帳號",[106,593,495],{},[106,595,596],{},"不依賴公司 AD／RADIUS，在 OrpheLink 自行管理",[85,598,599,602,604],{},[106,600,601],{},"財務部只允許財務群組員工",[106,603,506],{},[106,605,606],{},"用公司既有群組管理人員異動",[85,608,609,612,614],{},[106,610,611],{},"所有 AD 員工都需要基本存取",[106,613,517],{},[106,615,616],{},"不必逐一建帳號，但要限制設備並評估 MFA",[85,618,619,622,624],{},[106,620,621],{},"只允許某位外包工程師",[106,623,527],{},[106,625,626],{},"限定完整的個人 RADIUS 帳號",[85,628,629,636,638],{},[106,630,631,632,635],{},"只允許 RADIUS 回覆為 ",[532,633,634],{},"engineering"," 的成員",[106,637,542],{},[106,639,640],{},"依伺服器回傳的完整政策標籤授權",[85,642,643,646,648],{},[106,644,645],{},"該 Realm 下所有有效的 RADIUS 員工",[106,647,553],{},[106,649,650],{},"範圍很廣，應搭配特定設備與 MFA",[223,652,653],{"id":653},"運作方式",[42,655,656],{},"使用者端的操作不變：使用者在 OrpheAgent 或 Captive Portal 輸入帳密，OrpheLink Controller 再把帳密轉送到 AD（透過 LDAPS）或 RADIUS 驗證。接入企業帳號只需要在 OrpheLink 端設定。",[58,658,659],{},[42,660,661,662,665],{},"ℹ️ ",[45,663,664],{},"Auth source 決定「怎麼確認身分」，Authorized Devices 決定「通過後能去哪裡」。"," 兩者必須一起設定，且目標節點要開啟 Authentication。",[38,667,669],{"id":668},"四事前準備","四、事前準備",[671,672,673,676,679,685,691,697],"ul",{},[356,674,675],{},"有 OrpheLink Auth Connect 的檢視與編輯權限；目標 OrpheAgent 已完成 Provision 且連線正常，能在 Inventory 或 Neighbors 看到。",[356,677,678],{},"受保護的目標節點可在 OrpheLink 頁面中的 Node 或 Site 編輯頁設定 Authentication。",[356,680,681,684],{},[45,682,683],{},"使用 AD："," 備妥 LDAPS 憑證鏈、服務查詢帳號、Base DN 與使用者 UPN。",[356,686,687,690],{},[45,688,689],{},"使用 RADIUS："," 備妥伺服器位址與埠、Realm、各伺服器的 Shared Secret，以及可用於測試的 PAP 帳號。",[356,692,693,696],{},[45,694,695],{},"使用 MFA："," 使用者準備支援 TOTP 的驗證器（Google Authenticator、Microsoft Authenticator 或 iPhone 的「密碼」App），並確認 OrpheLink、OrpheAgent 與手機時間同步。",[356,698,699],{},"驗收時準備一個受保護的服務，用來檢查「未驗證被擋、驗證後放行」。",[79,701,702,712],{},[82,703,704],{},[85,705,706,709],{},[88,707,708],{},"您的情況",[88,710,711],{},"開始前先問管理員",[101,713,714,722,730,738],{},[85,715,716,719],{},[106,717,718],{},"公司沒有 AD／RADIUS，只想先測試",[106,720,721],{},"先用 Local Account，確認目標設備已連線",[85,723,724,727],{},[106,725,726],{},"員工平常使用 AD 帳號",[106,728,729],{},"請 IT 提供 AD 設定與可用群組；員工仍用個人帳密登入",[85,731,732,735],{},[106,733,734],{},"公司已有 RADIUS",[106,736,737],{},"請 IT 確認 Realm、Server、Shared Secret（只交給管理員）",[85,739,740,743],{},[106,741,742],{},"要讓使用者掃 QR Code",[106,744,745],{},"確認規則為 Required、授權有效，使用者有 TOTP 驗證器",[58,747,748],{},[42,749,750],{},"⚠️ 修改規則、Reset MFA 或停用來源，可能讓使用者無法建立新連線。正式環境請先準備可用的管理員登入與回復路徑。",[38,752,754],{"id":753},"五管理員設定","五、管理員設定",[223,756,758],{"id":757},"步驟-1開啟-auth-connect","步驟 1：開啟 Auth Connect",[353,760,761,764,774],{},[356,762,763],{},"登入 OrpheLink 管理介面。",[356,765,766,767,769,770],{},"在應用程式首頁點擊 ",[45,768,33],{},"。\n",[562,771],{"alt":772,"src":773},"圖 2｜OrpheLink 首頁：點擊 Auth Connect","\u002Fimages\u002Fmanual\u002Forphelink\u002Forphelink-setting\u002Fauth-connect\u002Fimage-02.webp",[356,775,776],{},"在清單查看既有規則，欄位包含 Account／Rule Name、Remark、Auth source、MFA Policy、Toggle、UpdatedAt 與 Action。",[42,778,779],{},[562,780],{"alt":781,"src":782},"圖 3｜Auth Connect 主畫面：規則清單與主要設定入口","\u002Fimages\u002Fmanual\u002Forphelink\u002Forphelink-setting\u002Fauth-connect\u002Fimage-03.webp",[79,784,785,795],{},[82,786,787],{},[85,788,789,792],{},[88,790,791],{},"按鈕",[88,793,794],{},"作用",[101,796,797,804,812,820,827,834],{},[85,798,799,801],{},[106,800,138],{},[106,802,803],{},"建立一條新的登入／授權規則；按 Apply 前不會儲存",[85,805,806,809],{},[106,807,808],{},"Action（編輯）",[106,810,811],{},"編輯名稱、說明、啟用狀態、設備範圍與 MFA 政策",[85,813,814,817],{},[106,815,816],{},"Toggle／Enable Rule",[106,818,819],{},"控制這條規則是否還能供新登入使用",[85,821,822,824],{},[106,823,117],{},[106,825,826],{},"管理 LDAPS Directory 連線與服務查詢資訊",[85,828,829,831],{},[106,830,121],{},[106,832,833],{},"管理 RADIUS 的 Realm、伺服器與連線測試",[85,835,836,839],{},[106,837,838],{},"MFA Settings",[106,840,841],{},"管理全域預設政策、Portal 首次綁定，與已綁定的身分",[58,843,844],{},[42,845,846],{},"ℹ️ 三個設定按鈕用途不同：按 Action 是改「這一條規則」；按 MFA Settings 是改「全域政策」或查看已綁定使用者；按 AD settings 是設定「公司的 AD 連線」。修改規則不會更動 AD 伺服器上的員工密碼。",[223,848,850],{"id":849},"步驟-2串接外部來源使用-ad-或-radius-時","步驟 2：串接外部來源（使用 AD 或 RADIUS 時）",[42,852,853],{},"只使用 Local Account 時，略過本步驟，直接到步驟 3。",[855,856,858],"h4",{"id":857},"a-串接-active-directoryad-settings","A. 串接 Active Directory（AD settings）",[353,860,861,871,893,906,916,923],{},[356,862,863,864,866,867,870],{},"點擊 ",[45,865,117],{},"，開啟 ",[45,868,869],{},"Enable Active Directory","。",[356,872,873,874,877,878,881,882,885,886,769,889],{},"輸入 ",[45,875,876],{},"LDAPS endpoints","（主要與備援，格式例如 ",[532,879,880],{},"ldaps:\u002F\u002F主機:636","）、",[45,883,884],{},"Base DN","、",[45,887,888],{},"UPN suffixes",[562,890],{"alt":891,"src":892},"圖 4｜AD settings（上半）：啟用 Directory、LDAPS 與服務帳號","\u002Fimages\u002Fmanual\u002Forphelink\u002Forphelink-setting\u002Fauth-connect\u002Fimage-04.webp",[356,894,873,895,898,899,902,903,870],{},[45,896,897],{},"Service Account UPN \u002F DN"," 與 ",[45,900,901],{},"Service Account Password","。這組帳號只用來查詢 AD 的使用者與群組，",[45,904,905],{},"不是員工的登入帳號",[356,907,908,909,912,913,870],{},"依 AD 憑證鏈貼上 ",[45,910,911],{},"Trusted CA certificates","（PEM 格式），再點擊 ",[45,914,915],{},"Test connection",[356,917,918,919,922],{},"查看 ",[45,920,921],{},"Connection Diagnostics","，確認 LDAPS Connection、TLS Certificate Validation、Service Account Bind、Base DN Lookup 與 Test Connection Result 都顯示 Passed。",[356,924,925,926,929],{},"測試通過後按 ",[45,927,928],{},"Apply"," 儲存；不想套用就按 Cancel。",[42,931,932],{},[562,933],{"alt":934,"src":935},"圖 5｜AD settings（下半）：Trusted CA certificates 與 Connection Diagnostics（尚未測試）","\u002Fimages\u002Fmanual\u002Forphelink\u002Forphelink-setting\u002Fauth-connect\u002Fimage-05.webp",[58,937,938,941],{},[42,939,940],{},"⚠️ AD 只支援經憑證驗證的 LDAPS。不要因為連線失敗而關閉 TLS 憑證驗證。Test connection 不會代替儲存，也不代表所有 AD 使用者已獲得設備授權。",[42,942,661,943,946,947,950],{},[45,944,945],{},"服務帳號與員工帳號不同："," 服務帳號像圖書館的「管理員查詢證」，只協助 OrpheLink 查詢員工與群組。員工登入時仍輸入自己的完整 AD 帳號（例如 ",[532,948,949],{},"xiaoming@example.com","）與個人密碼。串接完成後，還要建立至少一條已啟用的 AD Group 或 All AD Users 規則，員工才能登入。",[855,952,954],{"id":953},"b-串接-radiusradius-settings","B. 串接 RADIUS（RADIUS settings）",[353,956,957,964,978,1003,1010,1020],{},[356,958,863,959,866,961,870],{},[45,960,121],{},[45,962,963],{},"Enable RADIUS",[356,965,966,967,970,971,974,975,870],{},"填寫 ",[45,968,969],{},"RADIUS realm suffixes","（以逗號分隔）、",[45,972,973],{},"Forward Username","（Full username (UPN) 或 Strip Realm），視需求填寫 ",[45,976,977],{},"NAS Identifier",[356,979,980,981,984,985,988,989,885,992,995,996,769,999],{},"設定 ",[45,982,983],{},"Timeout (seconds)","，並在 ",[45,986,987],{},"Primary RADIUS Server"," 填入 ",[45,990,991],{},"Server Address",[45,993,994],{},"Authentication Port (UDP)","（預設 1812）與 ",[45,997,998],{},"Shared Secret",[562,1000],{"alt":1001,"src":1002},"圖 6｜RADIUS settings（上半）：Realm、轉送格式、NAS 與主伺服器","\u002Fimages\u002Fmanual\u002Forphelink\u002Forphelink-setting\u002Fauth-connect\u002Fimage-06.webp",[356,1004,1005,1006,1009],{},"需要備援時，點擊 ",[45,1007,1008],{},"Add Backup Server"," 設定第二台伺服器；只有一台時不需要。",[356,1011,1012,1013,1016,1017,1019],{},"在 ",[45,1014,1015],{},"Test Authentication"," 輸入一次性的 Test Username (UPN) 與 Test Password，點擊 ",[45,1018,1015],{},"。測試帳密不會被儲存。",[356,1021,1022,1023,1025],{},"結果正確後按 ",[45,1024,928],{},"，再到主清單建立對應的 RADIUS 規則。",[42,1027,1028],{},[562,1029],{"alt":1030,"src":1031},"圖 7｜RADIUS settings（下半）：備援伺服器與 Test Authentication","\u002Fimages\u002Fmanual\u002Forphelink\u002Forphelink-setting\u002Fauth-connect\u002Fimage-07.webp",[58,1033,1034,1041],{},[42,1035,1036,1037,1040],{},"ℹ️ RADIUS 只負責驗證外部密碼，使用者能連到哪些設備，仍由 OrpheLink 的規則決定。",[45,1038,1039],{},"Test Authentication 成功，只代表「外部櫃檯核對帳密成功」","，不代表使用者已符合 Authorized Devices 或 MFA。Forward Username 設為 Strip Realm 時，使用者登入 OrpheLink 與 MFA 的身分仍使用完整帳號。",[42,1042,1043],{},"⚠️ 只有連線逾時才會嘗試備援伺服器；Access-Reject、Access-Challenge 或訊息完整性失敗，不會被當作可安全重試的備援情境。",[223,1045,1047],{"id":1046},"步驟-3建立規則add","步驟 3：建立規則（Add）",[42,1049,1050],{},"規則決定「用哪種來源、哪些帳號、能連哪些設備、要不要 MFA」。共同的設定欄位：",[79,1052,1053,1063],{},[82,1054,1055],{},[85,1056,1057,1060],{},[88,1058,1059],{},"欄位",[88,1061,1062],{},"說明",[101,1064,1065,1073,1081,1089,1097],{},[85,1066,1067,1070],{},[106,1068,1069],{},"Rule Name（Local 為 Account Name）",[106,1071,1072],{},"規則名稱",[85,1074,1075,1078],{},[106,1076,1077],{},"Enable Rule（Local 為 Enable）",[106,1079,1080],{},"是否啟用",[85,1082,1083,1086],{},[106,1084,1085],{},"MFA Policy",[106,1087,1088],{},"Inherit Global、Disabled、Optional、Required（見步驟 5）",[85,1090,1091,1094],{},[106,1092,1093],{},"Authorized Devices（Local 為 Devices）",[106,1095,1096],{},"All Devices 或 Selected Devices（見步驟 4）",[85,1098,1099,1102],{},[106,1100,1101],{},"Description（Local 為 Remark）",[106,1103,1104],{},"說明用途，方便管理辨識",[855,1106,495],{"id":1107},"local-account",[353,1109,1110,1121,1132,1141,1151],{},[356,1111,1112,1113,1115,1116,1118,1119,870],{},"在 Auth Connect 點擊 ",[45,1114,138],{},"，",[45,1117,421],{}," 選 ",[45,1120,495],{},[356,1122,873,1123,885,1126,885,1129,870],{},[45,1124,1125],{},"Account Name",[45,1127,1128],{},"Password",[45,1130,1131],{},"Confirm Password",[356,1133,1134,1135,1138,1139,870],{},"保持 ",[45,1136,1137],{},"Enable"," 開啟，選擇 ",[45,1140,1085],{},[356,1142,1012,1143,1146,1147,1150],{},[45,1144,1145],{},"Devices"," 選 All Devices 或 Selected Devices，並在 ",[45,1148,1149],{},"Remark"," 記下用途。",[356,1152,1153,1154,1156],{},"按 ",[45,1155,928],{},"，回到主清單確認新規則出現。",[42,1158,1159],{},[562,1160],{"alt":1161,"src":1162},"圖 8｜Local Account 新增表單","\u002Fimages\u002Fmanual\u002Forphelink\u002Forphelink-setting\u002Fauth-connect\u002Fimage-08.webp",[58,1164,1165],{},[42,1166,1167],{},"⚠️ 手冊與截圖請勿保存真實密碼。刪除並重建同名的 Local 帳號，等同新的身分，原本的 MFA 綁定與恢復碼不會沿用。",[42,1169,1170,1173,1174,1177,1178,1180,1181,1184],{},[45,1171,1172],{},"範例：給外部顧問一週的測試帳號。"," 想讓外部顧問 ",[532,1175,1176],{},"guest-demo"," 在測試期間只能連一台測試機，不能連財務伺服器：Add → Local Account，填入 ",[532,1179,1176],{}," 與密碼 → Devices 選 ",[45,1182,1183],{},"Selected Devices","，只勾選測試機 → MFA Policy 視需求選 Required → Apply，並確認測試機的 Authentication 已開啟。顧問登入後連測試機成功，改連財務伺服器則被拒絕。",[855,1186,506],{"id":1187},"ad-group",[353,1189,1190,1198,1204,1212,1223],{},[356,1191,863,1192,1115,1194,1118,1196,870],{},[45,1193,138],{},[45,1195,421],{},[45,1197,506],{},[356,1199,1012,1200,1203],{},[45,1201,1202],{},"Allowed AD Group"," 搜尋並選取對應的 Security Group。下拉清單會列出 AD 伺服器上的群組（例如 Domain Admins、Domain Users）。",[356,1205,873,1206,866,1209,870],{},[45,1207,1208],{},"Rule Name",[45,1210,1211],{},"Enable Rule",[356,1213,1214,1215,898,1217,1219,1220,870],{},"選擇 ",[45,1216,1085],{},[45,1218,429],{},"，視需求填寫 ",[45,1221,1222],{},"Description",[356,1224,1153,1225,1227],{},[45,1226,928],{},"，檢查規則的啟用狀態與設備範圍。",[42,1229,1230],{},[562,1231],{"alt":1232,"src":1233},"圖 9｜AD Group 規則：Allowed AD Group、Rule Name、MFA Policy、Authorized Devices","\u002Fimages\u002Fmanual\u002Forphelink\u002Forphelink-setting\u002Fauth-connect\u002Fimage-09.webp",[79,1235,1236,1249],{},[82,1237,1238],{},[85,1239,1240,1243,1246],{},[88,1241,1242],{},"員工",[88,1244,1245],{},"是否屬於「財務」AD Group",[88,1247,1248],{},"連財務伺服器",[101,1250,1251,1262,1273],{},[85,1252,1253,1256,1259],{},[106,1254,1255],{},"小明（財務部）",[106,1257,1258],{},"是",[106,1260,1261],{},"密碼、設備授權、節點 Authentication 與 MFA 都符合，可通過",[85,1263,1264,1267,1270],{},[106,1265,1266],{},"小華（研發部）",[106,1268,1269],{},"否",[106,1271,1272],{},"無法靠這條財務規則通過",[85,1274,1275,1278,1281],{},[106,1276,1277],{},"新進財務員工",[106,1279,1280],{},"加入群組後",[106,1282,1283],{},"符合同一規則即可使用，不必另外建 Local 帳號",[58,1285,1286],{},[42,1287,1288],{},"ℹ️ 規則建立後，所選群組的身分識別會受到保護；若要更換驗證對象，請建立新規則並核對設備關聯。若同時存在符合條件的 All AD Users 廣泛規則，使用者仍可能透過那條規則獲得授權，請一併檢查。",[855,1290,517],{"id":1291},"all-ad-users",[353,1293,1294,1302,1309,1318],{},[356,1295,863,1296,1115,1298,1118,1300,870],{},[45,1297,138],{},[45,1299,421],{},[45,1301,517],{},[356,1303,873,1304,1306,1307,870],{},[45,1305,1208],{}," 並開啟 ",[45,1308,1211],{},[356,1310,1311,1312,1314,1315,1317],{},"將 ",[45,1313,429],{}," 設為 ",[45,1316,1183],{},"，避免無意授權所有設備。",[356,1319,1320,1321,1323,1324,870],{},"指定 ",[45,1322,1085],{}," 後按 ",[45,1325,928],{},[42,1327,1328],{},[562,1329],{"alt":1330,"src":1331},"圖 10｜All AD Users：仍須設定規則啟用、MFA 與設備範圍","\u002Fimages\u002Fmanual\u002Forphelink\u002Forphelink-setting\u002Fauth-connect\u002Fimage-10.webp",[58,1333,1334],{},[42,1335,1336],{},"ℹ️ All AD Users 並不會自動開放所有內網設備，但涵蓋的身分範圍很廣，正式環境建議搭配最小必要的設備授權與 MFA。例如規則只選「員工入口伺服器」，所有有效的 AD 使用者在完成 MFA 後可存取入口伺服器，但不會因此進入「財務機密伺服器」。",[855,1338,527],{"id":1339},"radius-user",[353,1341,1342,1350,1360,1365],{},[356,1343,863,1344,1115,1346,1118,1348,870],{},[45,1345,138],{},[45,1347,421],{},[45,1349,527],{},[356,1351,1012,1352,1355,1356,1359],{},[45,1353,1354],{},"Full RADIUS Username"," 輸入完整的帳號與 Realm（例如 ",[532,1357,1358],{},"wang@radius.example.test","）。",[356,1361,1362,1363,870],{},"輸入 Rule Name，選擇 MFA Policy 與 Authorized Devices，按 ",[45,1364,928],{},[356,1366,1367],{},"使用者以該帳號的 RADIUS 密碼在 OrpheAgent 驗證。",[42,1369,1370],{},[562,1371],{"alt":1372,"src":1373},"圖 11｜RADIUS - User：Full RADIUS Username 與適用設備","\u002Fimages\u002Fmanual\u002Forphelink\u002Forphelink-setting\u002Fauth-connect\u002Fimage-11.webp",[58,1375,1376],{},[42,1377,1378,1379,1382],{},"ℹ️ 另一位帳號（例如 ",[532,1380,1381],{},"li@radius.example.test","）即使 RADIUS 密碼正確，也不能靠這條指定帳號的規則登入。",[855,1384,542],{"id":1385},"radius-policy-filter-id",[353,1387,1388,1396,1406,1411],{},[356,1389,863,1390,1115,1392,1118,1394,870],{},[45,1391,138],{},[45,1393,421],{},[45,1395,542],{},[356,1397,1398,1399,1402,1403,870],{},"輸入 RADIUS Access-Accept ",[45,1400,1401],{},"實際回傳","的完整 ",[45,1404,1405],{},"Filter-Id",[356,1407,1408,1409,870],{},"設定 Rule Name、Enable Rule、MFA Policy 與 Authorized Devices，按 ",[45,1410,928],{},[356,1412,1413],{},"用已設定對應 Filter-Id 的測試帳號驗證。",[42,1415,1416],{},[562,1417],{"alt":1418,"src":1419},"圖 12｜RADIUS - Policy：Filter-Id 必須完整符合伺服器回覆","\u002Fimages\u002Fmanual\u002Forphelink\u002Forphelink-setting\u002Fauth-connect\u002Fimage-12.webp",[42,1421,1422,1423,1426],{},"Filter-Id 是",[45,1424,1425],{},"完整值比對","，不是模糊搜尋：",[79,1428,1429,1444],{},[82,1430,1431],{},[85,1432,1433,1436,1441],{},[88,1434,1435],{},"RADIUS 回覆的 Filter-Id",[88,1437,1438,1439],{},"規則中輸入 ",[532,1440,634],{},[88,1442,1443],{},"結果",[101,1445,1446,1458,1471,1483],{},[85,1447,1448,1452,1455],{},[106,1449,1450],{},[532,1451,634],{},[106,1453,1454],{},"完全相同",[106,1456,1457],{},"可進入後續的設備與 MFA 檢查",[85,1459,1460,1465,1468],{},[106,1461,1462],{},[532,1463,1464],{},"Engineering",[106,1466,1467],{},"大小寫不同",[106,1469,1470],{},"不能靠這條規則授權",[85,1472,1473,1478,1481],{},[106,1474,1475],{},[532,1476,1477],{},"engineering-extra",[106,1479,1480],{},"只有部分相同",[106,1482,1470],{},[85,1484,1485,1488,1491],{},[106,1486,1487],{},"沒有提供 Filter-Id",[106,1489,1490],{},"缺少政策標籤",[106,1492,1470],{},[58,1494,1495],{},[42,1496,1497,1498,1500],{},"ℹ️ Filter-Id 標籤必須先在 RADIUS 伺服器設定（例如把研發員工標為 ",[532,1499,634],{},"），OrpheLink 不會自動猜測部門。",[855,1502,553],{"id":1503},"radius-all-users",[353,1505,1506,1514],{},[356,1507,863,1508,1115,1510,1118,1512,870],{},[45,1509,138],{},[45,1511,421],{},[45,1513,553],{},[356,1515,1516,1517,1519],{},"設定 Rule Name、啟用狀態、MFA Policy 與 Authorized Devices，按 ",[45,1518,928],{},"，並確認目標節點已啟用 Authentication。",[42,1521,1522],{},[562,1523],{"alt":1524,"src":1525},"圖 13｜RADIUS - All Users：以設備範圍與 MFA 控制廣泛身分","\u002Fimages\u002Fmanual\u002Forphelink\u002Forphelink-setting\u002Fauth-connect\u002Fimage-13.webp",[58,1527,1528],{},[42,1529,1530],{},"⚠️ 同時有 RADIUS - All Users 與 User／Policy 規則時，必須一起檢查所有會授權該設備的規則。例如 All Users 規則已允許財務伺服器，即使另建精確的主管專用規則，也不會自動取消 All Users 的廣泛授權；請移除不需要的設備範圍，或停用該規則。",[223,1532,1534],{"id":1533},"步驟-4設定設備授權authorized-devices","步驟 4：設定設備授權（Authorized Devices）",[42,1536,1537],{},"帳號正確還不夠，使用者還必須被授權連到該設備。可以把它想成三道門：",[79,1539,1540,1552],{},[82,1541,1542],{},[85,1543,1544,1547,1550],{},[88,1545,1546],{},"問題",[88,1548,1549],{},"例子",[88,1551,1443],{},[101,1553,1554,1565,1576],{},[85,1555,1556,1559,1562],{},[106,1557,1558],{},"第一道：這個人是誰？",[106,1560,1561],{},"小明的 AD 密碼正確",[106,1563,1564],{},"通過身分驗證，但還不代表能連所有設備",[85,1566,1567,1570,1573],{},[106,1568,1569],{},"第二道：能進哪台設備？",[106,1571,1572],{},"小明只被授權「辦公室 NAS」",[106,1574,1575],{},"無法靠這條規則進入「財務伺服器」",[85,1577,1578,1581,1584],{},[106,1579,1580],{},"第三道：該設備啟用驗證了嗎？",[106,1582,1583],{},"NAS 的 Authentication 已開啟並收到設定",[106,1585,1586],{},"系統才能依授權規則攔截與驗證",[79,1588,1589,1598],{},[82,1590,1591],{},[85,1592,1593,1596],{},[88,1594,1595],{},"選項",[88,1597,1443],{},[101,1599,1600,1608],{},[85,1601,1602,1605],{},[106,1603,1604],{},"All Devices",[106,1606,1607],{},"自動涵蓋同一 Customer 內目前與未來的目標設備；目標節點仍需啟用 Authentication",[85,1609,1610,1612],{},[106,1611,1183],{},[106,1613,1614,1615,1618],{},"只涵蓋勾選的設備；",[45,1616,1617],{},"空集合代表不授權任何設備","，不會退回 All Devices",[42,1620,1621],{},[562,1622],{"alt":1623,"src":1624},"圖 14｜Selected Devices：把授權限制在指定的 OrpheAgent","\u002Fimages\u002Fmanual\u002Forphelink\u002Forphelink-setting\u002Fauth-connect\u002Fimage-14.webp",[58,1626,1627],{},[42,1628,1629],{},"⚠️ 以客服共用帳號為例：選 All Devices 時，這條規則會對同一 Customer 的現有與未來設備生效，不一定符合最小權限；只勾選「客服應用伺服器」時，即使之後新增財務伺服器，也不會自動加入這個帳號的可用清單。",[223,1631,1633],{"id":1632},"步驟-5設定-mfa-政策","步驟 5：設定 MFA 政策",[855,1635,1637],{"id":1636},"全域設定mfa-settings","全域設定（MFA Settings）",[353,1639,1640,1645,1655,1661,1667],{},[356,1641,1642,1643,870],{},"在 Auth Connect 主畫面點擊 ",[45,1644,838],{},[356,1646,980,1647,1650,1651,1654],{},[45,1648,1649],{},"Default MFA Policy","（Disabled、Optional 或 Required）。預設為 ",[45,1652,1653],{},"Disabled","，要使用 MFA 必須由 IT 管理員開啟。這個預設值只適用於 MFA Policy 設為 Inherit Global 的規則。",[356,1656,980,1657,1660],{},[45,1658,1659],{},"Authenticator Issuer Name","，也就是使用者驗證器裡顯示的名稱。",[356,1662,1663,1664,870],{},"依企業政策設定 ",[45,1665,1666],{},"Allow First-Time Enrollment on HTTP Portal",[356,1668,1153,1669,1671],{},[45,1670,928],{}," 儲存。",[42,1673,1674],{},[562,1675],{"alt":1676,"src":1677},"圖 15｜MFA Settings：預設政策、Issuer 與 HTTP Portal 首次綁定開關","\u002Fimages\u002Fmanual\u002Forphelink\u002Forphelink-setting\u002Fauth-connect\u002Fimage-15.webp",[58,1679,1680],{},[42,1681,1682],{},"ℹ️ 「Allow First-Time Enrollment on HTTP Portal」關閉後，只限制尚未綁定的身分透過 Portal 首次綁定；桌面版 OrpheAgent 的首次綁定，以及已綁定使用者在 Portal 的驗證，仍可依授權政策操作。",[855,1684,1686],{"id":1685},"每條規則的-mfa-policy","每條規則的 MFA Policy",[79,1688,1689,1702],{},[82,1690,1691],{},[85,1692,1693,1696,1699],{},[88,1694,1695],{},"規則的 MFA Policy",[88,1697,1698],{},"未綁定的使用者",[88,1700,1701],{},"已綁定的使用者",[101,1703,1704,1714,1725,1736],{},[85,1705,1706,1708,1711],{},[106,1707,1653],{},[106,1709,1710],{},"密碼正確即可通過",[106,1712,1713],{},"密碼正確即可通過，原綁定保留",[85,1715,1716,1719,1722],{},[106,1717,1718],{},"Optional",[106,1720,1721],{},"一般登入只要密碼",[106,1723,1724],{},"仍須輸入 TOTP 或 Recovery Code",[85,1726,1727,1730,1733],{},[106,1728,1729],{},"Required",[106,1731,1732],{},"先強制綁定 TOTP",[106,1734,1735],{},"每次新登入都須輸入 TOTP 或 Recovery Code",[85,1737,1738,1741,1744],{},[106,1739,1740],{},"Inherit Global",[106,1742,1743],{},"依 Default MFA Policy 判斷",[106,1745,1743],{},[42,1747,1748],{},[562,1749],{"alt":1750,"src":1751},"圖 16｜MFA Policy","\u002Fimages\u002Fmanual\u002Forphelink\u002Forphelink-setting\u002Fauth-connect\u002Fimage-16.webp",[58,1753,1754],{},[42,1755,661,1756,1759],{},[45,1757,1758],{},"Optional 的重點："," 它不是「登入時可自行略過 MFA」，也不是讓使用者主動選擇是否綁定。目前 OrpheAgent 桌面版與 Portal 沒有「主動綁定 MFA」的按鈕；已綁定的人必須輸入驗證碼，未綁定的人則只用密碼。若要讓使用者先完成綁定，管理員可先把規則設為 Required，綁定完成後再改回 Optional。",[42,1761,1762],{},[45,1763,1764],{},"實際案例：",[671,1766,1767,1773,1779,1785],{},[356,1768,1769,1772],{},[45,1770,1771],{},"Disabled：臨時測試機只核對密碼。"," 測試人員密碼正確，且設備授權與節點設定都符合，就能通過；即使他以前綁定過驗證器，這條規則也不會再要求輸入 6 位碼。Disabled 不會清除既有綁定，日後切回 Required，原綁定仍可繼續使用。",[356,1774,1775,1778],{},[45,1776,1777],{},"Optional：公司分階段導入 MFA。"," 小明還沒綁定，輸入正確的 AD 密碼即可登入；小華先前已綁定，即使規則是 Optional，仍須完成 TOTP 或使用未用過的 Recovery Code。",[356,1780,1781,1784],{},[45,1782,1783],{},"Required：IT 登入重要伺服器。"," 未綁定者依序完成：帳密 → 掃 QR 或輸入 Setup Key → 輸入 6 位碼 → Verify & Enroll → 保存 8 組 Recovery Codes。已綁定者輸入帳密後，輸入當期 6 位碼或一次性 Recovery Code。",[356,1786,1787,1790],{},[45,1788,1789],{},"Inherit Global：全公司統一管理。"," 多條規則都設為 Inherit Global，管理員把 Default MFA Policy 從 Disabled 改為 Required，這些規則的新登入就全部改採 Required，不必逐條修改。已明確設為 Disabled、Optional 或 Required 的規則，不會因為 Default 改變而自動變更。",[855,1792,1793],{"id":1793},"同一個人符合多條規則時",[42,1795,1796,1797,1800,1801,1804],{},"若同一使用者符合多條規則，而且這些規則都授權了他正在連的同一台設備，MFA 採",[45,1798,1799],{},"最嚴格","的有效政策：",[45,1802,1803],{},"Required 優先於 Optional，Optional 優先於 Disabled","。例如小華同時符合 Employees（Optional）與 IT（Required），這次登入就須完成 MFA。沒有授權該目標設備的規則，不會影響這次登入的 MFA 要求。",[855,1806,1808],{"id":1807},"如何選擇-mfa-政策","如何選擇 MFA 政策",[79,1810,1811,1823],{},[82,1812,1813],{},[85,1814,1815,1818,1821],{},[88,1816,1817],{},"實際用途",[88,1819,1820],{},"建議政策",[88,1822,584],{},[101,1824,1825,1836,1846,1856],{},[85,1826,1827,1830,1833],{},[106,1828,1829],{},"隔離的測試機（無敏感資料）",[106,1831,1832],{},"Disabled（視風險）",[106,1834,1835],{},"先驗證基本帳號登入流程",[85,1837,1838,1841,1843],{},[106,1839,1840],{},"員工分階段導入",[106,1842,1718],{},[106,1844,1845],{},"已綁定者維持 MFA，未綁定者暫用密碼",[85,1847,1848,1851,1853],{},[106,1849,1850],{},"IT、財務或重要伺服器",[106,1852,1729],{},[106,1854,1855],{},"每次新登入都須完成第二因素",[85,1857,1858,1861,1863],{},[106,1859,1860],{},"想由中央統一管理",[106,1862,1740],{},[106,1864,1865],{},"調整 Default MFA Policy 即可管理多條規則",[223,1867,1869],{"id":1868},"步驟-6在目標節點啟用-authentication關鍵步驟","步驟 6：在目標節點啟用 Authentication（關鍵步驟）",[42,1871,1872],{},"規則本身不會攔截流量。必須在受保護的目標節點開啟 Authentication，並選擇要套用的規則。",[353,1874,1875],{},[356,1876,1877],{},"開啟 OrpheLink 頁面",[42,1879,1880],{},[562,1881],{"alt":1882,"src":1883},"圖 17｜開啟 OrpheLink 管理後台","\u002Fimages\u002Fmanual\u002Forphelink\u002Forphelink-setting\u002Fauth-connect\u002Fimage-17.webp",[353,1885,1887],{"start":1886},2,[356,1888,1889],{},"找到目標 Site，開啟右上方的節點清單，再選擇要設定的 Node（設備）",[42,1891,1892],{},[562,1893],{"alt":1894,"src":1895},"圖 18｜進入目標節點的設定畫面","\u002Fimages\u002Fmanual\u002Forphelink\u002Forphelink-setting\u002Fauth-connect\u002Fimage-18.webp",[353,1897,1899,1908],{"start":1898},3,[356,1900,1901,1902,769,1904],{},"開啟 ",[45,1903,155],{},[562,1905],{"alt":1906,"src":1907},"圖 19｜在目標節點啟用 Authentication","\u002Fimages\u002Fmanual\u002Forphelink\u002Forphelink-setting\u002Fauth-connect\u002Fimage-19.webp",[356,1909,1012,1910,1913,1914,1917],{},[45,1911,1912],{},"Auth Connect Services"," 欄位，點擊 ",[45,1915,1916],{},"Add Auth Connect rule","，選擇步驟 3 建立的規則。",[42,1919,1920],{},[562,1921],{"alt":1922,"src":1923},"圖 20｜新增節點 Auth Connect 規則","\u002Fimages\u002Fmanual\u002Forphelink\u002Forphelink-setting\u002Fauth-connect\u002Fimage-20.webp",[353,1925,1927,1933],{"start":1926},5,[356,1928,980,1929,1932],{},[45,1930,1931],{},"Access timeout","（驗證通過後的存取有效時間；請依實際工作時長設定，避免無限制延長）。",[356,1934,1935],{},"儲存，並等待 OrpheAgent 在線接收設定。",[58,1937,1938],{},[42,1939,1940],{},"⚠️ 在節點取消勾選規則，不等於刪除共享規則，也不一定清除規則本身的 Devices 設定，調整後請在兩邊都檢查。若透過 Site 或 Template 套用規則，離線排程或等待中的 Template Apply，不代表受保護設備已在 runtime 生效；請檢查 Job 狀態，並用新的 session 實測。",[38,1942,1944],{"id":1943},"六使用者登入","六、使用者登入",[79,1946,1947,1960],{},[82,1948,1949],{},[85,1950,1951,1954,1957],{},[88,1952,1953],{},"使用者在做什麼",[88,1955,1956],{},"建議入口",[88,1958,1959],{},"成功後如何確認",[101,1961,1962,1972,1982],{},[85,1963,1964,1967,1969],{},[106,1965,1966],{},"在 OrpheAgent 想連某台 Neighbor",[106,1968,177],{},[106,1970,1971],{},"能存取該受保護資源",[85,1973,1974,1977,1979],{},[106,1975,1976],{},"瀏覽器連 HTTP 服務，跳出登入頁",[106,1978,461],{},[106,1980,1981],{},"驗證後回到原服務並能存取",[85,1983,1984,1987,1990],{},[106,1985,1986],{},"瀏覽器用 HTTPS，沒有出現 Portal",[106,1988,1989],{},"改用 Data Plane Auth",[106,1991,1992],{},"不要把 HTTPS 的連線錯誤當成已放行",[223,1994,1996],{"id":1995},"方式-aorpheagent-桌面版-data-plane-auth","方式 A：OrpheAgent 桌面版 Data Plane Auth",[42,1998,1999],{},"支援 macOS、Windows、Linux，三個平台的步驟相同。",[353,2001,2002,2009,2014,2020,2028],{},[356,2003,2004,2005,2008],{},"開啟 OrpheAgent，確認 ",[45,2006,2007],{},"Connect"," 已開啟、Data Plane 連線正常。",[356,2010,2011,2012,870],{},"在 Neighbors 標題旁，點擊 ",[45,2013,177],{},[356,2015,1012,2016,2019],{},[45,2017,2018],{},"Neighbor"," 選擇要連入的目標設備（顯示其 Tunnel IP）。",[356,2021,873,2022,898,2025,2027],{},[45,2023,2024],{},"Username",[45,2026,1128],{},"。AD 與 RADIUS 請輸入各自完整的 UPN／Realm 身分。",[356,2029,863,2030,2033],{},[45,2031,2032],{},"Authenticate","，依有效的 MFA Policy 完成後續驗證。",[42,2035,2036],{},[562,2037],{"alt":2038,"src":2039},"圖 21｜Data Plane Auth：選擇 Neighbor，輸入 Username 與 Password","\u002Fimages\u002Fmanual\u002Forphelink\u002Forphelink-setting\u002Fauth-connect\u002Fimage-21.webp",[42,2041,2042,2045],{},[45,2043,2044],{},"完整的登入故事："," 小華在家要連公司測試機。她開啟 OrpheAgent，點 Data Plane Auth，Neighbor 選測試機，輸入個人帳密。因為她曾綁定 MFA，下一個畫面不是 QR，而是 6 位數碼欄位；輸入手機上最新的驗證碼並按 Verify，就完成這次授權。",[223,2047,2049],{"id":2048},"首次-mfa-綁定規則為-required-時","首次 MFA 綁定（規則為 Required 時）",[58,2051,2052],{},[42,2053,2054,2055,2058],{},"⚠️ 本節與下方的 Portal 畫面，是依目前 OrpheAgent 與 Portal 前端重建的",[45,2056,2057],{},"操作示意","，畫面使用不可用的示範資料，請勿掃描示意 QR，或輸入其中的占位值。",[353,2060,2061,2068,2075,2081],{},[356,2062,2063,2064],{},"輸入帳密後，若這個身分需要首次綁定，畫面會顯示 QR Code、Setup Key 與 6 位驗證碼欄位。先確認畫面顯示的是自己的帳號，不要掃描別人的綁定畫面。\n",[562,2065],{"alt":2066,"src":2067},"圖 22｜首次綁定：掃描 QR、Copy Setup Key 與 Verify & Enroll（操作示意）（QR 已變造，僅供示意）","\u002Fimages\u002Fmanual\u002Forphelink\u002Forphelink-setting\u002Fauth-connect\u002Fimage-22.webp",[356,2069,2070,2071,2074],{},"在手機驗證器新增帳號，掃描 QR Code；無法掃描時，點 ",[45,2072,2073],{},"Copy Setup Key"," 並手動輸入。iPhone 使用者可在「密碼」App 的驗證碼視窗找到對應名稱。",[356,2076,2077,2078,870],{},"輸入驗證器目前顯示的 6 位數，點擊 ",[45,2079,2080],{},"Verify & Enroll",[356,2082,2083,2084,2087,2088,2091,2092,2095,2096,870],{},"系統顯示 ",[45,2085,2086],{},"8 組一次性 Recovery Codes","，點擊 ",[45,2089,2090],{},"Copy Recovery Codes"," 存放到安全位置，勾選 ",[45,2093,2094],{},"I have saved these recovery codes","，再按 ",[45,2097,2098],{},"Done",[42,2100,2101],{},[562,2102],{"alt":2103,"src":2104},"圖 23｜首次綁定成功：8 組 Recovery Codes 與保存確認（操作示意）","\u002Fimages\u002Fmanual\u002Forphelink\u002Forphelink-setting\u002Fauth-connect\u002Fimage-23.webp",[58,2106,2107],{},[42,2108,2109,2110,2113],{},"⚠️ 未完成 Verify & Enroll 之前，受保護的服務不會放行。恢復碼格式為 ",[532,2111,2112],{},"XXXX-XXXX-XXXX","，只在綁定完成後顯示一次，不要存在截圖、聊天室或公用雲端筆記。",[223,2115,2116],{"id":2116},"日常登入",[42,2118,2119,2120,2123,2124,2127],{},"已綁定的身分不會再看到 QR。輸入帳密後，畫面只會出現 ",[45,2121,2122],{},"Code"," 欄位：輸入驗證器目前的 6 位數，點擊 ",[45,2125,2126],{},"Verify","。同一個 30 秒時間步長的驗證碼不能重複使用。",[42,2129,2130],{},[562,2131],{"alt":2132,"src":2133},"圖 24｜日常登入：輸入 6 位 TOTP 驗證碼後按 Verify（操作示意）","\u002Fimages\u002Fmanual\u002Forphelink\u002Forphelink-setting\u002Fauth-connect\u002Fimage-24.webp",[223,2135,2136],{"id":2136},"手機遺失或無法使用驗證器",[353,2138,2139,2145,2151],{},[356,2140,2141,2142,870],{},"勾選 ",[45,2143,2144],{},"Use a single-use recovery code instead",[356,2146,2147,2148,2150],{},"輸入一組尚未使用的完整 Recovery Code（",[532,2149,2112],{},"），不是 6 位 TOTP。",[356,2152,2153],{},"成功後，該組恢復碼就失效，其他未使用的恢復碼仍保留。請盡快聯絡管理員重設 MFA。",[42,2155,2156],{},[562,2157],{"alt":2158,"src":2159},"圖 25｜替代登入：勾選 Use a single-use recovery code instead（操作示意）","\u002Fimages\u002Fmanual\u002Forphelink\u002Forphelink-setting\u002Fauth-connect\u002Fimage-25.webp",[58,2161,2162],{},[42,2163,2164],{},"ℹ️ Recovery Code 不是可重複使用的第二組密碼。小明換新手機時，若還有舊手機，應先處理驗證器移轉；舊手機已遺失，可使用未用過的恢復碼；連恢復碼都沒有，需請管理員重設該身分的 MFA。",[223,2166,2168],{"id":2167},"方式-b瀏覽器-captive-portal","方式 B：瀏覽器 Captive Portal",[42,2170,2171,2172,2175],{},"當使用者存取受保護的 HTTP 服務，瀏覽器會自動導向 ",[45,2173,2174],{},"OrpheLink Captive Portal","，操作邏輯與 OrpheAgent 一致。",[353,2177,2178,2181,2197],{},[356,2179,2180],{},"從瀏覽器連向受保護的 HTTP 服務，讓 Authentication 流程導向 Captive Portal。",[356,2182,2183,2184,898,2187,2189,2190,769,2193],{},"在 Portal 輸入 Auth Connect 的 ",[45,2185,2186],{},"User Name",[45,2188,1128],{},"。這裡輸入的是 Auth Connect 個人身分，",[45,2191,2192],{},"不是 OrpheLink 管理後台的帳密",[562,2194],{"alt":2195,"src":2196},"圖 26｜Captive Portal：User Name 與 Password 登入（操作示意）","\u002Fimages\u002Fmanual\u002Forphelink\u002Forphelink-setting\u002Fauth-connect\u002Fimage-26.webp",[356,2198,2199],{},"規則為 Required 且尚未綁定時，依 QR 或 Manual Setup Key 完成 TOTP 綁定，",[42,2201,2202],{},[562,2203],{"alt":2204,"src":2205},"圖 27｜Portal 首次 MFA 綁定：QR、Manual Setup Key、6-Digit Verification Code（操作示意）（QR 已變造，僅供示意）","\u002Fimages\u002Fmanual\u002Forphelink\u002Forphelink-setting\u002Fauth-connect\u002Fimage-27.webp",[353,2207,2209,2227],{"start":2208},4,[356,2210,2211,2212,2215,2216,2219,2220,769,2223],{},"用 ",[45,2213,2214],{},"Copy Codes"," 或 ",[45,2217,2218],{},"Download .txt"," 安全保存 Recovery Codes，勾選保存確認後按 ",[45,2221,2222],{},"Continue",[562,2224],{"alt":2225,"src":2226},"圖 28｜Portal 完成綁定：8 組恢復碼、Copy Codes、Download .txt（操作示意）","\u002Fimages\u002Fmanual\u002Forphelink\u002Forphelink-setting\u002Fauth-connect\u002Fimage-28.webp",[356,2228,2229],{},"已綁定時，輸入驗證器的 6 位碼",[42,2231,2232],{},[562,2233],{"alt":2234,"src":2235},"圖 29｜Portal 日常登入：輸入 6 位驗證碼（操作示意）","\u002Fimages\u002Fmanual\u002Forphelink\u002Forphelink-setting\u002Fauth-connect\u002Fimage-29.webp",[42,2237,2238,2239,870],{},"如需要時點擊 ",[45,2240,2241],{},"Use a recovery code instead",[42,2243,2244],{},[562,2245],{"alt":2246,"src":2247},"圖 30｜Portal 替代驗證：Use a recovery code instead（操作示意）","\u002Fimages\u002Fmanual\u002Forphelink\u002Forphelink-setting\u002Fauth-connect\u002Fimage-30.webp",[353,2249,2250],{"start":1926},[356,2251,2252],{},"驗證成功後回到原本的 HTTP 服務重新嘗試，以服務是否可用確認授權。",[58,2254,2255],{},[42,2256,661,2257,2260,2261,2264],{},[45,2258,2259],{},"Portal 與 OrpheAgent 的差別："," Portal 像飯店 Wi-Fi 連線前出現的登入頁，只是驗證的是企業資源的存取。Portal 主要由 ",[45,2262,2263],{},"HTTP"," 流量觸發；HTTPS 或 QUIC 的瀏覽器不一定會自動開啟 Portal，可能只顯示連線錯誤，這不代表可以略過驗證，也不代表沒有啟用 Auth Connect，請改用 OrpheAgent 的 Data Plane Auth。若管理員關閉了「Allow First-Time Enrollment on HTTP Portal」，從未綁定的使用者不能在 Portal 首次綁定，請改用 OrpheAgent 桌面版。",[38,2266,2268],{"id":2267},"七管理與維護","七、管理與維護",[79,2270,2271,2281],{},[82,2272,2273],{},[85,2274,2275,2278],{},[88,2276,2277],{},"操作",[88,2279,2280],{},"影響與注意事項",[101,2282,2283,2291,2299,2307,2315,2323],{},[85,2284,2285,2288],{},[106,2286,2287],{},"Edit／Apply",[106,2289,2290],{},"儲存規則；改了 Devices 或 MFA 政策後，請重開檢查設定，並用新的 session 驗證",[85,2292,2293,2296],{},[106,2294,2295],{},"Cancel",[106,2297,2298],{},"放棄尚未儲存的表單",[85,2300,2301,2304],{},[106,2302,2303],{},"Disable Rule",[106,2305,2306],{},"阻止之後不再被其他規則授權的新登入；既有 session 不會即時撤銷",[85,2308,2309,2312],{},[106,2310,2311],{},"Delete Rule",[106,2313,2314],{},"永久移除該規則；若有節點或 Template 引用，需另外核對",[85,2316,2317,2320],{},[106,2318,2319],{},"Reset MFA",[106,2321,2322],{},"移除選定身分的 MFA 綁定與恢復碼；下一次登入依政策重新綁定，不會立刻切斷既有連線",[85,2324,2325,2328],{},[106,2326,2327],{},"停用 AD／RADIUS settings",[106,2329,2330],{},"阻止對該外部來源建立新的有效驗證；不代表回收已開啟的 session",[42,2332,2333,2336,2337,2340],{},[45,2334,2335],{},"查看已綁定使用者："," 在 MFA Settings 的 ",[45,2338,2339],{},"Enrolled User Identities","，可搜尋並依身分來源檢視剩餘恢復碼數量（Recovery Codes Left）、綁定時間與最後驗證時間。",[42,2342,2343,2346],{},[45,2344,2345],{},"重設 MFA："," 使用者換手機、驗證器遺失，或沒有恢復碼時，管理員在這裡對該身分執行 Reset MFA。請先核對身分來源與帳號，避免重設到同名的另一個身分。Reset MFA 不是刪除帳號。",[58,2348,2349,2355],{},[42,2350,661,2351,2354],{},[45,2352,2353],{},"為什麼改了規則，使用者還能連？"," 已建立的 Data Plane session，在原本的有效時間內可能仍可連線。例如小明下午 2:00 驗證成功，2:01 管理員停用他的規則，他的連線仍可能持續。請確認新規則已儲存，停止對目標的流量、等待 session 逾時，再重新發起登入，確認新政策是否阻擋。不要用「按 Cancel 或關閉視窗」判斷已登出。",[42,2356,2357],{},"⚠️ 請避免直接修改正在使用的身分密碼，或 Reset 正在使用者手機中的 MFA。正式變更前，先記下原始的規則、設備範圍與 timeout，以便復原。",[38,2359,2361],{"id":2360},"八orphelink-管理後台登入的-mfa","八、OrpheLink 管理後台登入的 MFA",[42,2363,2364,2365,2368],{},"除了資料面的 Auth Connect MFA，OrpheLink 的",[45,2366,2367],{},"管理後台登入","也支援 MFA。這是另一套機制，與前面的規則無關。",[671,2370,2371,2377],{},[356,2372,2373,2376],{},[45,2374,2375],{},"已有OrpheLink帳號："," 登入時若系統提示開啟多重要素驗證（MFA），可點選 Enable MFA 開始設定；若暫時不設定，可點選 Not now, sign in 略過並直接登入。",[356,2378,2379],{},[45,2380,2381],{},"啟用 MFA 設定步驟:",[353,2383,2384,2387,2390,2393],{},[356,2385,2386],{},"綁定驗證器（左圖）：使用 Authenticator 應用程式（如 Google Authenticator、Microsoft Authenticator 或 Apple「密碼」）掃描畫面中的 QR 碼，或手動輸入下方金鑰（Setup key）。",[356,2388,2389],{},"輸入驗證碼：在下方欄位輸入 App 產生的 6 位數驗證碼，並點選 SIGN IN。",[356,2391,2392],{},"保存復原代碼（右圖）：驗證成功後系統會顯示一組復原代碼（Recovery codes）。請點選 Download 下載，或妥善儲存在此裝置以外的安全位置。",[356,2394,2395,2396],{},"完成啟用：勾選「I have saved my recovery codes securely」，再點選 Confirm 即完成設定。\n",[562,2397],{"alt":2398,"src":2399},"圖 31｜管理後台登入 MFA 畫面（QR Code、金鑰與恢復碼皆為無效示意）","\u002Fimages\u002Fmanual\u002Forphelink\u002Forphelink-setting\u002Fauth-connect\u002Fimage-31.webp",[58,2401,2402],{},[42,2403,2404],{},"⚠️ 重要提醒：復原代碼僅會顯示一次，每組代碼限用一次，且會直接覆蓋先前的舊代碼。請勿與他人分享，以確保帳號安全。",[671,2406,2407],{},[356,2408,2409],{},[45,2410,2411],{},"自行開啟或關閉多重要素驗證（MFA）：",[353,2413,2414,2417,2420,2423],{},[356,2415,2416],{},"進入設定頁面：前往 Settings → Account。",[356,2418,2419],{},"開啟編輯視窗：在 Multi-factor authentication (MFA) 項目旁，點擊 Edit 按鈕。",[356,2421,2422],{},"勾選或取消啟用：在彈出的設定視窗中，勾選或取消勾選 Enable multi-factor authentication。",[356,2424,2425],{},"儲存變更：點擊 Apply 即可完成設定（若放棄修改請點選 Cancel）。",[42,2427,2428],{},[562,2429],{"alt":2430,"src":2431},"圖 32｜Settings → Account：MFA","\u002Fimages\u002Fmanual\u002Forphelink\u002Forphelink-setting\u002Fauth-connect\u002Fimage-32.webp",[58,2433,2434,2437],{},[42,2435,2436],{},"⚠️ 注意事項：",[671,2438,2439,2442],{},[356,2440,2441],{},"啟用 MFA 後，未來每次登入皆需要進行驗證。首次啟用者將在下一次登入時完成驗證器綁定。",[356,2443,2444],{},"變更此設定可能需要輸入您目前的帳號密碼以確保安全。",[671,2446,2447],{},[356,2448,2449],{},[45,2450,2451],{},"重新產生復原代碼（Recovery codes）:",[353,2453,2454,2456,2459,2470,2473],{},[356,2455,2416],{},[356,2457,2458],{},"開啟復原代碼視窗：在 Multi-factor authentication (MFA) 項目旁，點擊 Recovery codes 按鈕。",[356,2460,2461,2462],{},"身分安全驗證：在彈出的視窗中，分別輸入：",[671,2463,2464,2467],{},[356,2465,2466],{},"Current password：您目前的帳號密碼。",[356,2468,2469],{},"6-digit verification code：驗證器 App 產生的最新 6 位數動態驗證碼。",[356,2471,2472],{},"產生新代碼：點擊 Generate new recovery codes。",[356,2474,2475],{},"下載並保存新代碼：系統產生全新代碼後，請立即點選下載或妥善保存至安全處所",[42,2477,2478],{},[562,2479],{"alt":2480,"src":2481},"圖 33｜檢視與保存管理後台的 MFA 恢復碼","\u002Fimages\u002Fmanual\u002Forphelink\u002Forphelink-setting\u002Fauth-connect\u002Fimage-33.webp",[58,2483,2484,2486],{},[42,2485,2436],{},[671,2487,2488,2491,2494],{},[356,2489,2490],{},"舊代碼即刻失效：產生新代碼後，將會直接取代並作廢所有先前的復原代碼。",[356,2492,2493],{},"強制登出既有連線：執行此操作會強制登出目前所有裝置的登入階段（Existing sessions）。",[356,2495,2496],{},"請務必先保存代碼：請在再次登入系統前，確認已將全新代碼妥善備份保存。",[671,2498,2499],{},[356,2500,2501,2504],{},[45,2502,2503],{},"MFA 重新綁定與管理員協助（Reset MFA）","：",[353,2506,2507],{},[356,2508,2509,2512],{},[45,2510,2511],{},"個人設定限制","：使用者啟用 MFA 後，在個人設定中僅能選擇「啟用\u002F停用」或「重新產生 Recovery codes」，無法自行重新掃描 QR Code 重新綁定驗證器。",[671,2514,2515,2521],{},[356,2516,2517,2518,870],{},"**重置情境：**若使用者更換手機、更換 Authenticator App、遺失驗證碼且遺失 Recovery codes 時，必須尋求管理員協助執行 ",[45,2519,2520],{},"Reset multi-factor authentication",[356,2522,2523,2524],{},"重置申請管道與權責劃分：",[671,2525,2526,2529],{},[356,2527,2528],{},"在地部署 \u002F 組織自管帳號：可由組織內的具管理員權限帳號，直接至後台替該成員重置 MFA。",[356,2530,2531],{},"雲端使用者（Cloud User）：因雲端系統最高管理員為 O'Prueba，若雲端帳號無法登入，使用者需透過登入畫面上提供的聯絡支援信箱來信提出申請。O'Prueba 團隊核對客戶身分資料無誤後，將會協助後台重置 MFA，完成後使用者即可於下次登入時重新掃描 QR Code 進行綁定。",[38,2533,2535],{"id":2534},"九驗收確認-auth-connect-真的生效","九、驗收：確認 Auth Connect 真的生效",[42,2537,2538],{},"驗收時要分別確認「未驗證確實被擋」與「驗證後確實放行」，不能只憑登入成功訊息判斷服務有效。",[353,2540,2541,2554,2560,2566],{},[356,2542,2543,2546,2547,2550,2551,870],{},[45,2544,2545],{},"未登入時被擋："," 在用戶端 Ping 目標節點的 Tunnel IP，會看到 ",[45,2548,2549],{},"Communication prohibited by filter","，這是驗證前的封包過濾回應，與一般網路逾時不同。用 Chrome 開啟 HTTPS 網站時，可能出現 ",[45,2552,2553],{},"ERR_SSL_PROTOCOL_ERROR",[356,2555,2556,2559],{},[45,2557,2558],{},"登入後放行："," 完成 Data Plane Auth 或 Portal 驗證後，實際開啟要使用的服務，確認可以存取。",[356,2561,2562,2565],{},[45,2563,2564],{},"未授權的設備仍被擋："," 用同一帳號連不在 Authorized Devices 內的設備，應被拒絕。",[356,2567,2568,2571],{},[45,2569,2570],{},"錯誤的驗證碼無法通過："," 輸入錯誤或已使用的碼，不應放行。",[42,2573,2574],{},[562,2575],{"alt":2576,"src":2577},"圖 34｜未驗證時，Chrome 可能顯示 ERR_SSL_PROTOCOL_ERROR","\u002Fimages\u002Fmanual\u002Forphelink\u002Forphelink-setting\u002Fauth-connect\u002Fimage-34.webp",[58,2579,2580],{},[42,2581,2582],{},"ℹ️ Neighbors 顯示 Online／Good，只代表通道可被發現，不代表使用者已通過驗證。SSL 錯誤本身不能單獨證明 Authentication 正常，仍需另外檢查 HTTPS、路由與憑證。看到「Authentication succeeded」字樣後，也請實際開啟服務確認，它不保證所有後續應用操作都會成功。",[38,2584,2586],{"id":2585},"十常見問題與排除","十、常見問題與排除",[42,2588,2589],{},"排錯前先問自己四個問題：",[353,2591,2592,2595,2598,2601],{},[356,2593,2594],{},"我選的目標設備正確嗎？",[356,2596,2597],{},"我的登入來源對嗎？Local 帳號與 AD、RADIUS 帳號不一定能互換。",[356,2599,2600],{},"我的帳號有被授權這台設備嗎？密碼正確也可能因為 Devices 範圍不符而失敗。",[356,2602,2603],{},"我是否完成了目前要求的 MFA？6 位碼可能過期，Recovery Code 可能已用過。",[79,2605,2606,2616],{},[82,2607,2608],{},[85,2609,2610,2613],{},[88,2611,2612],{},"狀況",[88,2614,2615],{},"建議檢查",[101,2617,2618,2626,2634,2642,2650,2658,2666,2674,2682,2690,2698,2706,2714,2722],{},[85,2619,2620,2623],{},[106,2621,2622],{},"建立了規則，流量卻沒有被驗證",[106,2624,2625],{},"確認目標節點已開啟 Authentication、已套用規則，且節點已收到更新後的設定",[85,2627,2628,2631],{},[106,2629,2630],{},"帳密正確但登入被拒絕",[106,2632,2633],{},"核對規則是否啟用、身分來源、Devices 範圍、節點關聯，並先排除舊的 session",[85,2635,2636,2639],{},[106,2637,2638],{},"AD Test connection 失敗",[106,2640,2641],{},"逐項檢查 LDAPS Endpoint、FQDN／SAN、受信任 CA、Service Account Bind 與 Base DN；不要降級為不驗證憑證",[85,2643,2644,2647],{},[106,2645,2646],{},"RADIUS 測試成功但仍無法存取",[106,2648,2649],{},"Test 只測密碼；請檢查規則、Realm、User／Policy、Filter-Id、授權設備與 MFA",[85,2651,2652,2655],{},[106,2653,2654],{},"AD 帳號登入失敗",[106,2656,2657],{},"請輸入完整 UPN；確認帳號屬於規則的 AD Group（或規則為 All AD Users）",[85,2659,2660,2663],{},[106,2661,2662],{},"首次 Required 沒有出現 QR",[106,2664,2665],{},"檢查該身分是否已綁定、有效政策是否為 Required、Portal 首次綁定是否被關閉、Controller 與 Agent 版本是否一致",[85,2667,2668,2671],{},[106,2669,2670],{},"TOTP 顯示 invalid verification code",[106,2672,2673],{},"確認手機時間同步、輸入最新的碼、沒有使用舊 QR 或重複使用同一個 30 秒的碼，並留意是否被鎖定",[85,2675,2676,2679],{},[106,2677,2678],{},"Recovery Code 不能使用",[106,2680,2681],{},"確認輸入完整的碼、是否已用過，或身分是否被 Reset；必要時請管理員精確重設 MFA",[85,2683,2684,2687],{},[106,2685,2686],{},"改了規則，服務仍然能連",[106,2688,2689],{},"舊 session 不會立即撤銷；停止流量、等待 timeout 後重新確認",[85,2691,2692,2695],{},[106,2693,2694],{},"瀏覽器沒有出現 Captive Portal",[106,2696,2697],{},"確認受保護的 HTTP 流量可觸發攔截；HTTPS 或 QUIC 情境改用 Data Plane Auth",[85,2699,2700,2703],{},[106,2701,2702],{},"目標節點離線，規則沒有生效",[106,2704,2705],{},"確認所選節點在線、設定已派送且已被接收，不要只看 Controller 已儲存",[85,2707,2708,2711],{},[106,2709,2710],{},"失敗次數過多被鎖定",[106,2712,2713],{},"停止連續重試，等待鎖定結束，或由管理員評估 Reset",[85,2715,2716,2719],{},[106,2717,2718],{},"開啟 Service White List 後無法登入 Portal",[106,2720,2721],{},"確認已有 Authentication、TCP、Port 81 的規則（系統通常會自動加入）",[85,2723,2724,2727],{},[106,2725,2726],{},"設定 Auth Connect 與 Device Auth 搞混",[106,2728,2729],{},"Device Auth 授權設備加入網路；Auth Connect 是使用者存取受保護服務的驗證",[42,2731,2732,2733],{},"若顯示驗證成功但仍無法使用服務，請告訴 IT：連線目標、登入時間、遇到的錯誤，以及是否完成 MFA。",[45,2734,2735],{},"不要提供密碼或驗證碼。",[38,2737,2739],{"id":2738},"十一安全建議","十一、安全建議",[671,2741,2742,2745,2748,2751,2754],{},[356,2743,2744],{},"All AD Users 與 RADIUS - All Users 涵蓋的身分很廣，建議搭配 Selected Devices、Required MFA 與最小權限。",[356,2746,2747],{},"AD 服務帳號密碼、RADIUS Shared Secret、MFA Setup Key、QR Code 與 Recovery Codes，不應出現在手冊、日誌、截圖或版本控制中。",[356,2749,2750],{},"設備搬移、Leave 或重新 Provision 後，請重新確認規則的 Devices、節點的 Authentication 與 MFA 身分範圍。",[356,2752,2753],{},"備份 OrpheLink Controller 資料庫時，MFA、Directory 與 RADIUS 的密文金鑰需依維運文件一併保存；缺少金鑰時，不可直接重新產生來覆蓋既有綁定。",[356,2755,2756],{},"一般使用者：先詢問 IT 要用 Local、AD 還是 RADIUS；不要把管理員帳密當成一般使用者帳密；第一次被要求 MFA 時，妥善保存 8 組恢復碼，不要把真正的 QR 或 Key 傳到聊天軟體。",{"title":2758,"searchDepth":1886,"depth":1886,"links":2759},"",[2760,2761,2762,2768,2769,2773,2774,2782,2789,2790,2791,2792,2793],{"id":40,"depth":1886,"text":33},{"id":73,"depth":1886,"text":74},{"id":209,"depth":1886,"text":210,"children":2763},[2764,2765,2766,2767],{"id":225,"depth":1898,"text":225},{"id":231,"depth":1898,"text":231},{"id":293,"depth":1898,"text":293},{"id":348,"depth":1898,"text":348},{"id":378,"depth":1886,"text":379},{"id":467,"depth":1886,"text":468,"children":2770},[2771,2772],{"id":568,"depth":1898,"text":569},{"id":653,"depth":1898,"text":653},{"id":668,"depth":1886,"text":669},{"id":753,"depth":1886,"text":754,"children":2775},[2776,2777,2778,2779,2780,2781],{"id":757,"depth":1898,"text":758},{"id":849,"depth":1898,"text":850},{"id":1046,"depth":1898,"text":1047},{"id":1533,"depth":1898,"text":1534},{"id":1632,"depth":1898,"text":1633},{"id":1868,"depth":1898,"text":1869},{"id":1943,"depth":1886,"text":1944,"children":2783},[2784,2785,2786,2787,2788],{"id":1995,"depth":1898,"text":1996},{"id":2048,"depth":1898,"text":2049},{"id":2116,"depth":1898,"text":2116},{"id":2136,"depth":1898,"text":2136},{"id":2167,"depth":1898,"text":2168},{"id":2267,"depth":1886,"text":2268},{"id":2360,"depth":1886,"text":2361},{"id":2534,"depth":1886,"text":2535},{"id":2585,"depth":1886,"text":2586},{"id":2738,"depth":1886,"text":2739},"OrpheLink Auth Connect 整合 Local、AD、RADIUS 身分來源與 TOTP MFA，搭配 Authorized Devices 授權規則，控管 OrpheAgent Data Plane 的使用者登入與設備存取。","md","tw",{},60,"orphelink\u002Forphelink-setting","\u002Fmanual\u002Ftw\u002Forphelink\u002Forphelink-setting\u002Fauth-connect","orphelink\u002Forphelink-setting\u002Fauth-connect","orphelink","Auth Connect OrpheLink Auth Connect 是 Data Plane 的使用者身分驗證機制。整合 Local \u002F AD \u002F RADIUS 身分來源 與 TOTP MFA 雙重驗證 ，結合精確的設備授權規則，確保只有通過核准的使用者能存取指定設備。使用者可透過 OrpheAgent 桌面 GUI 或網頁 Captive Portal 快速完成登入。 設備連上網路之後，再確認「 正確的人 」只能存取「 被授權的設備 」。 支援 Local Account、Active Directory（AD）、RADIUS，以及 TOTP 多因素驗證（MFA）。 快速開始：5 步完成 Auth Connect 先看這一頁，了解整體流程；每一步的細節在後面的章節。 步驟 誰做 做什麼 完成的樣子 1 管理員 決定登入來源（Local／AD／RADIUS）。使用 AD 或 RADIUS 時，先在 AD settings ／ RADIUS settings 完成串接並測試 測試結果通過，按 Apply 儲存 2 管理員 在 Auth Connect 按 Add 建立規則，指定來源、可存取的設備（Authorized Devices）與 MFA Policy 規則出現在清單，Toggle 為 Enable 3 管理員 到目標節點開啟 Authentication ，選擇要套用的規則 節點收到設定（ 沒做這步，規則不會生效 ） 4 使用者 在 OrpheAgent 的 Data Plane Auth （或瀏覽器 Captive Portal）輸入帳號密碼；需要 MFA 時再輸入 6 位動態碼 可以連到被授權的設備 5 管理員 驗收：未登入時被擋、登入後放行、未授權的設備仍被擋 三項結果都符合預期 ⚠️ 最常見的錯誤： 建立了規則，卻忘記在目標節點開啟 Authentication。這種情況下流量不會被攔截，也不會要求登入。 一、功能說明 Auth Connect 是 OrpheLink 對 OrpheAgent 資料平面（Data Plane）的 使用者身分驗證 與 設備存取授權 功能。管理員建立登入規則，使用者通過驗證後，才能存取規則允許的設備。 為什麼需要它 設備顯示 Online，只代表加密通道建立了，不代表「現在坐在電腦前的人」有權使用。Auth Connect 在封包抵達受保護節點之前，要求使用者先證明身分與存取權限。 三大防線中的位置 防線 要回答的問題 驗證方式 第一道：設備認證（Device Auth） 哪台設備可以開通 Data Plane 加入網路？ 指定 Email ＋ Magic Link 核准 第二道：身分連線認證（Auth Connect） 誰正在使用這台設備存取目標資源？ 企業帳密（Local／AD／RADIUS）＋ TOTP MFA 第三道：服務白名單（Service White List） 這台設備只能連到對方的哪些 Port？ TCP\u002FUDP ＋ Port ＋ 允許的 Neighbor 範圍 Auth Connect 不會取代設備核准或防火牆規則，三者各自獨立驗證。 三個核心關卡 封包只有依序通過以下三關，才會被轉送： 關卡 要回答的問題 管理員在哪裡設定 身分來源（Auth source） 你是誰？ Add 規則時選擇；AD、RADIUS 另需串接設定 設備授權（Authorized Devices） 你能去哪？ 每條規則的 Devices／Authorized Devices MFA 政策（MFA Policy） 要不要多一道鎖？ MFA Settings 與每條規則的 MFA Policy 一個辦公室故事 公司有「辦公室檔案伺服器」與「研發測試機」。小明是一般員工，只能連檔案伺服器；小華是 IT 人員，可以連兩台，而且重要設備必須輸入手機驗證碼。 1. IT 管理員為小明、小華建立登入規則。 2. 管理員決定每條規則允許的設備：小明只有檔案伺服器。 3. 管理員為重要設備設定 MFA Required，並確認目標設備已開啟 Authentication。 4. 員工在 OrpheAgent 選擇目標設備並登入，必要時完成手機驗證碼。 5. 通過後才能連線到被允許的設備；不在清單內的設備仍會被拒絕。 ℹ️ 這裡的「登入成功」指的是資料面的存取授權，不代表能登入 OrpheLink 管理後台，也不代表對方設備本身的檔案權限全部開放。 二、名詞白話對照 介面上的字 白話說明 Auth Connect 管理「誰能用什麼方式登入、能連到哪些設備」的規則 OrpheLink 管理員設定規則的控制中心 OrpheAgent／Node／Neighbor 電腦上的連線程式／被管理的設備／清單中的另一台設備 Auth source 帳號密碼從哪裡驗證，例如 OrpheLink 自建、公司 AD、公司 RADIUS Authorized Devices 這條規則通過驗證後，可存取的目標設備範圍 MFA／TOTP 密碼之外，再用手機驗證器產生的 6 位數動態碼（每 30 秒更新） Recovery Code 手機無法產生驗證碼時使用的一次性備用碼 Session／Timeout 驗證通過後暫時有效的存取狀態，與其逾時時間 Captive Portal 因存取受保護網頁而跳出的瀏覽器登入畫面 三、身分來源：選擇登入方式 新增規則時，管理員在 Auth source 選擇帳號來源。使用者仍用熟悉的帳號密碼登入，不必改變習慣。 Auth source 驗證與授權方式 使用者登入時輸入 Local Account 帳號與密碼由 OrpheLink 規則管理 管理員建立的 Account Name 與密碼 AD Group AD 使用者須屬於指定的 Security Group，並通過個人密碼驗證 完整 UPN 與 AD 密碼 All AD Users 所有符合 Directory 與規則設備範圍的 AD 使用者 完整 UPN 與 AD 密碼 RADIUS User 指定單一完整的 username@realm 該帳號的 RADIUS 密碼 RADIUS Policy (Filter Id) 僅允許 Access Accept 回覆中帶有指定完整 Filter Id 的使用者 RADIUS 帳號與密碼 RADIUS All Users 符合 Realm 與設備範圍的 RADIUS 使用者都可嘗試驗證 RADIUS 帳號與密碼 該選哪一種？ 公司情境（示例） 適合的 Auth source 原因 訪客或測試人員需要一組暫時帳號 Local Account 不依賴公司 AD／RADIUS，在 OrpheLink 自行管理 財務部只允許財務群組員工 AD Group 用公司既有群組管理人員異動 所有 AD 員工都需要基本存取 All AD Users 不必逐一建帳號，但要限制設備並評估 MFA 只允許某位外包工程師 RADIUS User 限定完整的個人 RADIUS 帳號 只允許 RADIUS 回覆為 engineering 的成員 RADIUS Policy (Filter Id) 依伺服器回傳的完整政策標籤授權 該 Realm 下所有有效的 RADIUS 員工 RADIUS All Users 範圍很廣，應搭配特定設備與 MFA 運作方式 使用者端的操作不變：使用者在 OrpheAgent 或 Captive Portal 輸入帳密，OrpheLink Controller 再把帳密轉送到 AD（透過 LDAPS）或 RADIUS 驗證。接入企業帳號只需要在 OrpheLink 端設定。 ℹ️ Auth source 決定「怎麼確認身分」，Authorized Devices 決定「通過後能去哪裡」。 兩者必須一起設定，且目標節點要開啟 Authentication。 四、事前準備 有 OrpheLink Auth Connect 的檢視與編輯權限；目標 OrpheAgent 已完成 Provision 且連線正常，能在 Inventory 或 Neighbors 看到。 受保護的目標節點可在 OrpheLink 頁面中的 Node 或 Site 編輯頁設定 Authentication。 使用 AD： 備妥 LDAPS 憑證鏈、服務查詢帳號、Base DN 與使用者 UPN。 使用 RADIUS： 備妥伺服器位址與埠、Realm、各伺服器的 Shared Secret，以及可用於測試的 PAP 帳號。 使用 MFA： 使用者準備支援 TOTP 的驗證器（Google Authenticator、Microsoft Authenticator 或 iPhone 的「密碼」App），並確認 OrpheLink、OrpheAgent 與手機時間同步。 驗收時準備一個受保護的服務，用來檢查「未驗證被擋、驗證後放行」。 您的情況 開始前先問管理員 公司沒有 AD／RADIUS，只想先測試 先用 Local Account，確認目標設備已連線 員工平常使用 AD 帳號 請 IT 提供 AD 設定與可用群組；員工仍用個人帳密登入 公司已有 RADIUS 請 IT 確認 Realm、Server、Shared Secret（只交給管理員） 要讓使用者掃 QR Code 確認規則為 Required、授權有效，使用者有 TOTP 驗證器 ⚠️ 修改規則、Reset MFA 或停用來源，可能讓使用者無法建立新連線。正式環境請先準備可用的管理員登入與回復路徑。 五、管理員設定 步驟 1：開啟 Auth Connect 1. 登入 OrpheLink 管理介面。 2. 在應用程式首頁點擊 Auth Connect 。 3. 在清單查看既有規則，欄位包含 Account／Rule Name、Remark、Auth source、MFA Policy、Toggle、UpdatedAt 與 Action。 按鈕 作用 Add 建立一條新的登入／授權規則；按 Apply 前不會儲存 Action（編輯） 編輯名稱、說明、啟用狀態、設備範圍與 MFA 政策 Toggle／Enable Rule 控制這條規則是否還能供新登入使用 AD settings 管理 LDAPS Directory 連線與服務查詢資訊 RADIUS settings 管理 RADIUS 的 Realm、伺服器與連線測試 MFA Settings 管理全域預設政策、Portal 首次綁定，與已綁定的身分 ℹ️ 三個設定按鈕用途不同：按 Action 是改「這一條規則」；按 MFA Settings 是改「全域政策」或查看已綁定使用者；按 AD settings 是設定「公司的 AD 連線」。修改規則不會更動 AD 伺服器上的員工密碼。 步驟 2：串接外部來源（使用 AD 或 RADIUS 時） 只使用 Local Account 時，略過本步驟，直接到步驟 3。 A. 串接 Active Directory（AD settings） 1. 點擊 AD settings ，開啟 Enable Active Directory 。 2. 輸入 LDAPS endpoints （主要與備援，格式例如 ldaps:\u002F\u002F主機:636 ）、 Base DN 、 UPN suffixes 。 3. 輸入 Service Account UPN \u002F DN 與 Service Account Password 。這組帳號只用來查詢 AD 的使用者與群組， 不是員工的登入帳號 。 4. 依 AD 憑證鏈貼上 Trusted CA certificates （PEM 格式），再點擊 Test connection 。 5. 查看 Connection Diagnostics ，確認 LDAPS Connection、TLS Certificate Validation、Service Account Bind、Base DN Lookup 與 Test Connection Result 都顯示 Passed。 6. 測試通過後按 Apply 儲存；不想套用就按 Cancel。 ⚠️ AD 只支援經憑證驗證的 LDAPS。不要因為連線失敗而關閉 TLS 憑證驗證。Test connection 不會代替儲存，也不代表所有 AD 使用者已獲得設備授權。 ℹ️ 服務帳號與員工帳號不同： 服務帳號像圖書館的「管理員查詢證」，只協助 OrpheLink 查詢員工與群組。員工登入時仍輸入自己的完整 AD 帳號（例如 xiaoming@example.com ）與個人密碼。串接完成後，還要建立至少一條已啟用的 AD Group 或 All AD Users 規則，員工才能登入。 B. 串接 RADIUS（RADIUS settings） 1. 點擊 RADIUS settings ，開啟 Enable RADIUS 。 2. 填寫 RADIUS realm suffixes （以逗號分隔）、 Forward Username （Full username (UPN) 或 Strip Realm），視需求填寫 NAS Identifier 。 3. 設定 Timeout (seconds) ，並在 Primary RADIUS Server 填入 Server Address 、 Authentication Port (UDP) （預設 1812）與 Shared Secret 。 4. 需要備援時，點擊 Add Backup Server 設定第二台伺服器；只有一台時不需要。 5. 在 Test Authentication 輸入一次性的 Test Username (UPN) 與 Test Password，點擊 Test Authentication 。測試帳密不會被儲存。 6. 結果正確後按 Apply ，再到主清單建立對應的 RADIUS 規則。 ℹ️ RADIUS 只負責驗證外部密碼，使用者能連到哪些設備，仍由 OrpheLink 的規則決定。 Test Authentication 成功，只代表「外部櫃檯核對帳密成功」 ，不代表使用者已符合 Authorized Devices 或 MFA。Forward Username 設為 Strip Realm 時，使用者登入 OrpheLink 與 MFA 的身分仍使用完整帳號。 ⚠️ 只有連線逾時才會嘗試備援伺服器；Access Reject、Access Challenge 或訊息完整性失敗，不會被當作可安全重試的備援情境。 步驟 3：建立規則（Add） 規則決定「用哪種來源、哪些帳號、能連哪些設備、要不要 MFA」。共同的設定欄位： 欄位 說明 Rule Name（Local 為 Account Name） 規則名稱 Enable Rule（Local 為 Enable） 是否啟用 MFA Policy Inherit Global、Disabled、Optional、Required（見步驟 5） Authorized Devices（Local 為 Devices） All Devices 或 Selected Devices（見步驟 4） Description（Local 為 Remark） 說明用途，方便管理辨識 Local Account 1. 在 Auth Connect 點擊 Add ， Auth source 選 Local Account 。 2. 輸入 Account Name 、 Password 、 Confirm Password 。 3. 保持 Enable 開啟，選擇 MFA Policy 。 4. 在 Devices 選 All Devices 或 Selected Devices，並在 Remark 記下用途。 5. 按 Apply ，回到主清單確認新規則出現。 ⚠️ 手冊與截圖請勿保存真實密碼。刪除並重建同名的 Local 帳號，等同新的身分，原本的 MFA 綁定與恢復碼不會沿用。 範例：給外部顧問一週的測試帳號。 想讓外部顧問 guest demo 在測試期間只能連一台測試機，不能連財務伺服器：Add → Local Account，填入 guest demo 與密碼 → Devices 選 Selected Devices ，只勾選測試機 → MFA Policy 視需求選 Required → Apply，並確認測試機的 Authentication 已開啟。顧問登入後連測試機成功，改連財務伺服器則被拒絕。 AD Group 1. 點擊 Add ， Auth source 選 AD Group 。 2. 在 Allowed AD Group 搜尋並選取對應的 Security Group。下拉清單會列出 AD 伺服器上的群組（例如 Domain Admins、Domain Users）。 3. 輸入 Rule Name ，開啟 Enable Rule 。 4. 選擇 MFA Policy 與 Authorized Devices ，視需求填寫 Description 。 5. 按 Apply ，檢查規則的啟用狀態與設備範圍。 員工 是否屬於「財務」AD Group 連財務伺服器 小明（財務部） 是 密碼、設備授權、節點 Authentication 與 MFA 都符合，可通過 小華（研發部） 否 無法靠這條財務規則通過 新進財務員工 加入群組後 符合同一規則即可使用，不必另外建 Local 帳號 ℹ️ 規則建立後，所選群組的身分識別會受到保護；若要更換驗證對象，請建立新規則並核對設備關聯。若同時存在符合條件的 All AD Users 廣泛規則，使用者仍可能透過那條規則獲得授權，請一併檢查。 All AD Users 1. 點擊 Add ， Auth source 選 All AD Users 。 2. 輸入 Rule Name 並開啟 Enable Rule 。 3. 將 Authorized Devices 設為 Selected Devices ，避免無意授權所有設備。 4. 指定 MFA Policy 後按 Apply 。 ℹ️ All AD Users 並不會自動開放所有內網設備，但涵蓋的身分範圍很廣，正式環境建議搭配最小必要的設備授權與 MFA。例如規則只選「員工入口伺服器」，所有有效的 AD 使用者在完成 MFA 後可存取入口伺服器，但不會因此進入「財務機密伺服器」。 RADIUS User 1. 點擊 Add ， Auth source 選 RADIUS User 。 2. 在 Full RADIUS Username 輸入完整的帳號與 Realm（例如 wang@radius.example.test ）。 3. 輸入 Rule Name，選擇 MFA Policy 與 Authorized Devices，按 Apply 。 4. 使用者以該帳號的 RADIUS 密碼在 OrpheAgent 驗證。 ℹ️ 另一位帳號（例如 li@radius.example.test ）即使 RADIUS 密碼正確，也不能靠這條指定帳號的規則登入。 RADIUS Policy (Filter Id) 1. 點擊 Add ， Auth source 選 RADIUS Policy (Filter Id) 。 2. 輸入 RADIUS Access Accept 實際回傳 的完整 Filter Id 。 3. 設定 Rule Name、Enable Rule、MFA Policy 與 Authorized Devices，按 Apply 。 4. 用已設定對應 Filter Id 的測試帳號驗證。 Filter Id 是 完整值比對 ，不是模糊搜尋： RADIUS 回覆的 Filter Id 規則中輸入 engineering 結果 engineering 完全相同 可進入後續的設備與 MFA 檢查 Engineering 大小寫不同 不能靠這條規則授權 engineering extra 只有部分相同 不能靠這條規則授權 沒有提供 Filter Id 缺少政策標籤 不能靠這條規則授權 ℹ️ Filter Id 標籤必須先在 RADIUS 伺服器設定（例如把研發員工標為 engineering ），OrpheLink 不會自動猜測部門。 RADIUS All Users 1. 點擊 Add ， Auth source 選 RADIUS All Users 。 2. 設定 Rule Name、啟用狀態、MFA Policy 與 Authorized Devices，按 Apply ，並確認目標節點已啟用 Authentication。 ⚠️ 同時有 RADIUS All Users 與 User／Policy 規則時，必須一起檢查所有會授權該設備的規則。例如 All Users 規則已允許財務伺服器，即使另建精確的主管專用規則，也不會自動取消 All Users 的廣泛授權；請移除不需要的設備範圍，或停用該規則。 步驟 4：設定設備授權（Authorized Devices） 帳號正確還不夠，使用者還必須被授權連到該設備。可以把它想成三道門： 問題 例子 結果 第一道：這個人是誰？ 小明的 AD 密碼正確 通過身分驗證，但還不代表能連所有設備 第二道：能進哪台設備？ 小明只被授權「辦公室 NAS」 無法靠這條規則進入「財務伺服器」 第三道：該設備啟用驗證了嗎？ NAS 的 Authentication 已開啟並收到設定 系統才能依授權規則攔截與驗證 選項 結果 All Devices 自動涵蓋同一 Customer 內目前與未來的目標設備；目標節點仍需啟用 Authentication Selected Devices 只涵蓋勾選的設備； 空集合代表不授權任何設備 ，不會退回 All Devices ⚠️ 以客服共用帳號為例：選 All Devices 時，這條規則會對同一 Customer 的現有與未來設備生效，不一定符合最小權限；只勾選「客服應用伺服器」時，即使之後新增財務伺服器，也不會自動加入這個帳號的可用清單。 步驟 5：設定 MFA 政策 全域設定（MFA Settings） 1. 在 Auth Connect 主畫面點擊 MFA Settings 。 2. 設定 Default MFA Policy （Disabled、Optional 或 Required）。預設為 Disabled ，要使用 MFA 必須由 IT 管理員開啟。這個預設值只適用於 MFA Policy 設為 Inherit Global 的規則。 3. 設定 Authenticator Issuer Name ，也就是使用者驗證器裡顯示的名稱。 4. 依企業政策設定 Allow First Time Enrollment on HTTP Portal 。 5. 按 Apply 儲存。 ℹ️ 「Allow First Time Enrollment on HTTP Portal」關閉後，只限制尚未綁定的身分透過 Portal 首次綁定；桌面版 OrpheAgent 的首次綁定，以及已綁定使用者在 Portal 的驗證，仍可依授權政策操作。 每條規則的 MFA Policy 規則的 MFA Policy 未綁定的使用者 已綁定的使用者 Disabled 密碼正確即可通過 密碼正確即可通過，原綁定保留 Optional 一般登入只要密碼 仍須輸入 TOTP 或 Recovery Code Required 先強制綁定 TOTP 每次新登入都須輸入 TOTP 或 Recovery Code Inherit Global 依 Default MFA Policy 判斷 依 Default MFA Policy 判斷 ℹ️ Optional 的重點： 它不是「登入時可自行略過 MFA」，也不是讓使用者主動選擇是否綁定。目前 OrpheAgent 桌面版與 Portal 沒有「主動綁定 MFA」的按鈕；已綁定的人必須輸入驗證碼，未綁定的人則只用密碼。若要讓使用者先完成綁定，管理員可先把規則設為 Required，綁定完成後再改回 Optional。 實際案例： Disabled：臨時測試機只核對密碼。 測試人員密碼正確，且設備授權與節點設定都符合，就能通過；即使他以前綁定過驗證器，這條規則也不會再要求輸入 6 位碼。Disabled 不會清除既有綁定，日後切回 Required，原綁定仍可繼續使用。 Optional：公司分階段導入 MFA。 小明還沒綁定，輸入正確的 AD 密碼即可登入；小華先前已綁定，即使規則是 Optional，仍須完成 TOTP 或使用未用過的 Recovery Code。 Required：IT 登入重要伺服器。 未綁定者依序完成：帳密 → 掃 QR 或輸入 Setup Key → 輸入 6 位碼 → Verify & Enroll → 保存 8 組 Recovery Codes。已綁定者輸入帳密後，輸入當期 6 位碼或一次性 Recovery Code。 Inherit Global：全公司統一管理。 多條規則都設為 Inherit Global，管理員把 Default MFA Policy 從 Disabled 改為 Required，這些規則的新登入就全部改採 Required，不必逐條修改。已明確設為 Disabled、Optional 或 Required 的規則，不會因為 Default 改變而自動變更。 同一個人符合多條規則時 若同一使用者符合多條規則，而且這些規則都授權了他正在連的同一台設備，MFA 採 最嚴格 的有效政策： Required 優先於 Optional，Optional 優先於 Disabled 。例如小華同時符合 Employees（Optional）與 IT（Required），這次登入就須完成 MFA。沒有授權該目標設備的規則，不會影響這次登入的 MFA 要求。 如何選擇 MFA 政策 實際用途 建議政策 原因 隔離的測試機（無敏感資料） Disabled（視風險） 先驗證基本帳號登入流程 員工分階段導入 Optional 已綁定者維持 MFA，未綁定者暫用密碼 IT、財務或重要伺服器 Required 每次新登入都須完成第二因素 想由中央統一管理 Inherit Global 調整 Default MFA Policy 即可管理多條規則 步驟 6：在目標節點啟用 Authentication（關鍵步驟） 規則本身不會攔截流量。必須在受保護的目標節點開啟 Authentication，並選擇要套用的規則。 1. 開啟 OrpheLink 頁面 2. 找到目標 Site，開啟右上方的節點清單，再選擇要設定的 Node（設備） 3. 開啟 Authentication 。 4. 在 Auth Connect Services 欄位，點擊 Add Auth Connect rule ，選擇步驟 3 建立的規則。 5. 設定 Access timeout （驗證通過後的存取有效時間；請依實際工作時長設定，避免無限制延長）。 6. 儲存，並等待 OrpheAgent 在線接收設定。 ⚠️ 在節點取消勾選規則，不等於刪除共享規則，也不一定清除規則本身的 Devices 設定，調整後請在兩邊都檢查。若透過 Site 或 Template 套用規則，離線排程或等待中的 Template Apply，不代表受保護設備已在 runtime 生效；請檢查 Job 狀態，並用新的 session 實測。 六、使用者登入 使用者在做什麼 建議入口 成功後如何確認 在 OrpheAgent 想連某台 Neighbor Data Plane Auth 能存取該受保護資源 瀏覽器連 HTTP 服務，跳出登入頁 Captive Portal 驗證後回到原服務並能存取 瀏覽器用 HTTPS，沒有出現 Portal 改用 Data Plane Auth 不要把 HTTPS 的連線錯誤當成已放行 方式 A：OrpheAgent 桌面版 Data Plane Auth 支援 macOS、Windows、Linux，三個平台的步驟相同。 1. 開啟 OrpheAgent，確認 Connect 已開啟、Data Plane 連線正常。 2. 在 Neighbors 標題旁，點擊 Data Plane Auth 。 3. 在 Neighbor 選擇要連入的目標設備（顯示其 Tunnel IP）。 4. 輸入 Username 與 Password 。AD 與 RADIUS 請輸入各自完整的 UPN／Realm 身分。 5. 點擊 Authenticate ，依有效的 MFA Policy 完成後續驗證。 完整的登入故事： 小華在家要連公司測試機。她開啟 OrpheAgent，點 Data Plane Auth，Neighbor 選測試機，輸入個人帳密。因為她曾綁定 MFA，下一個畫面不是 QR，而是 6 位數碼欄位；輸入手機上最新的驗證碼並按 Verify，就完成這次授權。 首次 MFA 綁定（規則為 Required 時） ⚠️ 本節與下方的 Portal 畫面，是依目前 OrpheAgent 與 Portal 前端重建的 操作示意 ，畫面使用不可用的示範資料，請勿掃描示意 QR，或輸入其中的占位值。 1. 輸入帳密後，若這個身分需要首次綁定，畫面會顯示 QR Code、Setup Key 與 6 位驗證碼欄位。先確認畫面顯示的是自己的帳號，不要掃描別人的綁定畫面。 2. 在手機驗證器新增帳號，掃描 QR Code；無法掃描時，點 Copy Setup Key 並手動輸入。iPhone 使用者可在「密碼」App 的驗證碼視窗找到對應名稱。 3. 輸入驗證器目前顯示的 6 位數，點擊 Verify & Enroll 。 4. 系統顯示 8 組一次性 Recovery Codes ，點擊 Copy Recovery Codes 存放到安全位置，勾選 I have saved these recovery codes ，再按 Done 。 ⚠️ 未完成 Verify & Enroll 之前，受保護的服務不會放行。恢復碼格式為 XXXX XXXX XXXX ，只在綁定完成後顯示一次，不要存在截圖、聊天室或公用雲端筆記。 日常登入 已綁定的身分不會再看到 QR。輸入帳密後，畫面只會出現 Code 欄位：輸入驗證器目前的 6 位數，點擊 Verify 。同一個 30 秒時間步長的驗證碼不能重複使用。 手機遺失或無法使用驗證器 1. 勾選 Use a single use recovery code instead 。 2. 輸入一組尚未使用的完整 Recovery Code（ XXXX XXXX XXXX ），不是 6 位 TOTP。 3. 成功後，該組恢復碼就失效，其他未使用的恢復碼仍保留。請盡快聯絡管理員重設 MFA。 ℹ️ Recovery Code 不是可重複使用的第二組密碼。小明換新手機時，若還有舊手機，應先處理驗證器移轉；舊手機已遺失，可使用未用過的恢復碼；連恢復碼都沒有，需請管理員重設該身分的 MFA。 方式 B：瀏覽器 Captive Portal 當使用者存取受保護的 HTTP 服務，瀏覽器會自動導向 OrpheLink Captive Portal ，操作邏輯與 OrpheAgent 一致。 1. 從瀏覽器連向受保護的 HTTP 服務，讓 Authentication 流程導向 Captive Portal。 2. 在 Portal 輸入 Auth Connect 的 User Name 與 Password 。這裡輸入的是 Auth Connect 個人身分， 不是 OrpheLink 管理後台的帳密 。 3. 規則為 Required 且尚未綁定時，依 QR 或 Manual Setup Key 完成 TOTP 綁定， 4. 用 Copy Codes 或 Download .txt 安全保存 Recovery Codes，勾選保存確認後按 Continue 。 5. 已綁定時，輸入驗證器的 6 位碼 如需要時點擊 Use a recovery code instead 。 5. 驗證成功後回到原本的 HTTP 服務重新嘗試，以服務是否可用確認授權。 ℹ️ Portal 與 OrpheAgent 的差別： Portal 像飯店 Wi Fi 連線前出現的登入頁，只是驗證的是企業資源的存取。Portal 主要由 HTTP 流量觸發；HTTPS 或 QUIC 的瀏覽器不一定會自動開啟 Portal，可能只顯示連線錯誤，這不代表可以略過驗證，也不代表沒有啟用 Auth Connect，請改用 OrpheAgent 的 Data Plane Auth。若管理員關閉了「Allow First Time Enrollment on HTTP Portal」，從未綁定的使用者不能在 Portal 首次綁定，請改用 OrpheAgent 桌面版。 七、管理與維護 操作 影響與注意事項 Edit／Apply 儲存規則；改了 Devices 或 MFA 政策後，請重開檢查設定，並用新的 session 驗證 Cancel 放棄尚未儲存的表單 Disable Rule 阻止之後不再被其他規則授權的新登入；既有 session 不會即時撤銷 Delete Rule 永久移除該規則；若有節點或 Template 引用，需另外核對 Reset MFA 移除選定身分的 MFA 綁定與恢復碼；下一次登入依政策重新綁定，不會立刻切斷既有連線 停用 AD／RADIUS settings 阻止對該外部來源建立新的有效驗證；不代表回收已開啟的 session 查看已綁定使用者： 在 MFA Settings 的 Enrolled User Identities ，可搜尋並依身分來源檢視剩餘恢復碼數量（Recovery Codes Left）、綁定時間與最後驗證時間。 重設 MFA： 使用者換手機、驗證器遺失，或沒有恢復碼時，管理員在這裡對該身分執行 Reset MFA。請先核對身分來源與帳號，避免重設到同名的另一個身分。Reset MFA 不是刪除帳號。 ℹ️ 為什麼改了規則，使用者還能連？ 已建立的 Data Plane session，在原本的有效時間內可能仍可連線。例如小明下午 2:00 驗證成功，2:01 管理員停用他的規則，他的連線仍可能持續。請確認新規則已儲存，停止對目標的流量、等待 session 逾時，再重新發起登入，確認新政策是否阻擋。不要用「按 Cancel 或關閉視窗」判斷已登出。 ⚠️ 請避免直接修改正在使用的身分密碼，或 Reset 正在使用者手機中的 MFA。正式變更前，先記下原始的規則、設備範圍與 timeout，以便復原。 八、OrpheLink 管理後台登入的 MFA 除了資料面的 Auth Connect MFA，OrpheLink 的 管理後台登入 也支援 MFA。這是另一套機制，與前面的規則無關。 已有OrpheLink帳號： 登入時若系統提示開啟多重要素驗證（MFA），可點選 Enable MFA 開始設定；若暫時不設定，可點選 Not now, sign in 略過並直接登入。 啟用 MFA 設定步驟: 1. 綁定驗證器（左圖）：使用 Authenticator 應用程式（如 Google Authenticator、Microsoft Authenticator 或 Apple「密碼」）掃描畫面中的 QR 碼，或手動輸入下方金鑰（Setup key）。 2. 輸入驗證碼：在下方欄位輸入 App 產生的 6 位數驗證碼，並點選 SIGN IN。 3. 保存復原代碼（右圖）：驗證成功後系統會顯示一組復原代碼（Recovery codes）。請點選 Download 下載，或妥善儲存在此裝置以外的安全位置。 4. 完成啟用：勾選「I have saved my recovery codes securely」，再點選 Confirm 即完成設定。 ⚠️ 重要提醒：復原代碼僅會顯示一次，每組代碼限用一次，且會直接覆蓋先前的舊代碼。請勿與他人分享，以確保帳號安全。 自行開啟或關閉多重要素驗證（MFA）： 1. 進入設定頁面：前往 Settings → Account。 2. 開啟編輯視窗：在 Multi factor authentication (MFA) 項目旁，點擊 Edit 按鈕。 3. 勾選或取消啟用：在彈出的設定視窗中，勾選或取消勾選 Enable multi factor authentication。 4. 儲存變更：點擊 Apply 即可完成設定（若放棄修改請點選 Cancel）。 ⚠️ 注意事項： 啟用 MFA 後，未來每次登入皆需要進行驗證。首次啟用者將在下一次登入時完成驗證器綁定。 變更此設定可能需要輸入您目前的帳號密碼以確保安全。 重新產生復原代碼（Recovery codes）: 1. 進入設定頁面：前往 Settings → Account。 2. 開啟復原代碼視窗：在 Multi factor authentication (MFA) 項目旁，點擊 Recovery codes 按鈕。 3. 身分安全驗證：在彈出的視窗中，分別輸入： Current password：您目前的帳號密碼。 6 digit verification code：驗證器 App 產生的最新 6 位數動態驗證碼。 4. 產生新代碼：點擊 Generate new recovery codes。 5. 下載並保存新代碼：系統產生全新代碼後，請立即點選下載或妥善保存至安全處所 ⚠️ 注意事項： 舊代碼即刻失效：產生新代碼後，將會直接取代並作廢所有先前的復原代碼。 強制登出既有連線：執行此操作會強制登出目前所有裝置的登入階段（Existing sessions）。 請務必先保存代碼：請在再次登入系統前，確認已將全新代碼妥善備份保存。 MFA 重新綁定與管理員協助（Reset MFA） ： 1. 個人設定限制 ：使用者啟用 MFA 後，在個人設定中僅能選擇「啟用\u002F停用」或「重新產生 Recovery codes」，無法自行重新掃描 QR Code 重新綁定驗證器。 重置情境： 若使用者更換手機、更換 Authenticator App、遺失驗證碼且遺失 Recovery codes 時，必須尋求管理員協助執行 Reset multi factor authentication 。 重置申請管道與權責劃分： 在地部署 \u002F 組織自管帳號：可由組織內的具管理員權限帳號，直接至後台替該成員重置 MFA。 雲端使用者（Cloud User）：因雲端系統最高管理員為 O'Prueba，若雲端帳號無法登入，使用者需透過登入畫面上提供的聯絡支援信箱來信提出申請。O'Prueba 團隊核對客戶身分資料無誤後，將會協助後台重置 MFA，完成後使用者即可於下次登入時重新掃描 QR Code 進行綁定。 九、驗收：確認 Auth Connect 真的生效 驗收時要分別確認「未驗證確實被擋」與「驗證後確實放行」，不能只憑登入成功訊息判斷服務有效。 1. 未登入時被擋： 在用戶端 Ping 目標節點的 Tunnel IP，會看到 Communication prohibited by filter ，這是驗證前的封包過濾回應，與一般網路逾時不同。用 Chrome 開啟 HTTPS 網站時，可能出現 ERR SSL PROTOCOL ERROR 。 2. 登入後放行： 完成 Data Plane Auth 或 Portal 驗證後，實際開啟要使用的服務，確認可以存取。 3. 未授權的設備仍被擋： 用同一帳號連不在 Authorized Devices 內的設備，應被拒絕。 4. 錯誤的驗證碼無法通過： 輸入錯誤或已使用的碼，不應放行。 ℹ️ Neighbors 顯示 Online／Good，只代表通道可被發現，不代表使用者已通過驗證。SSL 錯誤本身不能單獨證明 Authentication 正常，仍需另外檢查 HTTPS、路由與憑證。看到「Authentication succeeded」字樣後，也請實際開啟服務確認，它不保證所有後續應用操作都會成功。 十、常見問題與排除 排錯前先問自己四個問題： 1. 我選的目標設備正確嗎？ 2. 我的登入來源對嗎？Local 帳號與 AD、RADIUS 帳號不一定能互換。 3. 我的帳號有被授權這台設備嗎？密碼正確也可能因為 Devices 範圍不符而失敗。 4. 我是否完成了目前要求的 MFA？6 位碼可能過期，Recovery Code 可能已用過。 狀況 建議檢查 建立了規則，流量卻沒有被驗證 確認目標節點已開啟 Authentication、已套用規則，且節點已收到更新後的設定 帳密正確但登入被拒絕 核對規則是否啟用、身分來源、Devices 範圍、節點關聯，並先排除舊的 session AD Test connection 失敗 逐項檢查 LDAPS Endpoint、FQDN／SAN、受信任 CA、Service Account Bind 與 Base DN；不要降級為不驗證憑證 RADIUS 測試成功但仍無法存取 Test 只測密碼；請檢查規則、Realm、User／Policy、Filter Id、授權設備與 MFA AD 帳號登入失敗 請輸入完整 UPN；確認帳號屬於規則的 AD Group（或規則為 All AD Users） 首次 Required 沒有出現 QR 檢查該身分是否已綁定、有效政策是否為 Required、Portal 首次綁定是否被關閉、Controller 與 Agent 版本是否一致 TOTP 顯示 invalid verification code 確認手機時間同步、輸入最新的碼、沒有使用舊 QR 或重複使用同一個 30 秒的碼，並留意是否被鎖定 Recovery Code 不能使用 確認輸入完整的碼、是否已用過，或身分是否被 Reset；必要時請管理員精確重設 MFA 改了規則，服務仍然能連 舊 session 不會立即撤銷；停止流量、等待 timeout 後重新確認 瀏覽器沒有出現 Captive Portal 確認受保護的 HTTP 流量可觸發攔截；HTTPS 或 QUIC 情境改用 Data Plane Auth 目標節點離線，規則沒有生效 確認所選節點在線、設定已派送且已被接收，不要只看 Controller 已儲存 失敗次數過多被鎖定 停止連續重試，等待鎖定結束，或由管理員評估 Reset 開啟 Service White List 後無法登入 Portal 確認已有 Authentication、TCP、Port 81 的規則（系統通常會自動加入） 設定 Auth Connect 與 Device Auth 搞混 Device Auth 授權設備加入網路；Auth Connect 是使用者存取受保護服務的驗證 若顯示驗證成功但仍無法使用服務，請告訴 IT：連線目標、登入時間、遇到的錯誤，以及是否完成 MFA。 不要提供密碼或驗證碼。 十一、安全建議 All AD Users 與 RADIUS All Users 涵蓋的身分很廣，建議搭配 Selected Devices、Required MFA 與最小權限。 AD 服務帳號密碼、RADIUS Shared Secret、MFA Setup Key、QR Code 與 Recovery Codes，不應出現在手冊、日誌、截圖或版本控制中。 設備搬移、Leave 或重新 Provision 後，請重新確認規則的 Devices、節點的 Authentication 與 MFA 身分範圍。 備份 OrpheLink Controller 資料庫時，MFA、Directory 與 RADIUS 的密文金鑰需依維運文件一併保存；缺少金鑰時，不可直接重新產生來覆蓋既有綁定。 一般使用者：先詢問 IT 要用 Local、AD 還是 RADIUS；不要把管理員帳密當成一般使用者帳密；第一次被要求 MFA 時，妥善保存 8 組恢復碼，不要把真正的 QR 或 Key 傳到聊天軟體。",{"title":33,"description":2794},"zh-TW","manual\u002Ftw\u002Forphelink\u002Forphelink-setting\u002Fauth-connect","1.2.1","cKChJtHG3y4iB4XplQ35SHCu0KvIOdIzt56b26CWJnw",[2810,2815,2820,2824,2828,2832,2836,2840,2844,2848,2852,2856,2860,2864,2868,2872,2876,2880,2884,2888,2892,2896,2900,2904,2908,2911,2915,2919,2923,2927,2931,2935,2939,2943,2947,2951,2955,2959,2962,2966,2969,2972,2976,2980,2984,2988,2992,2996,3000,3004,3008,3012,3016,3020,3024,3028,3032,3036,3040,3044,3048,3052,3056,3059,3063,3067,3071,3075,3079,3083,3086,3090,3094,3098,3102,3106,3110,3114,3118,3122,3126,3130,3134,3138,3143,3147,3151,3155,3159,3163,3167,3171,3175,3179,3182,3186,3188,3190,3192,3195,3197,3200,3203,3204,3207,3210,3213],{"path_key":2811,"parent_path":2758,"product":2811,"title":2812,"product_order":2813,"order":2814,"visible":24,"navigation":24,"sidebar":24},"oos","OOS",40,22,{"path_key":2816,"parent_path":2758,"product":2816,"title":2817,"product_order":2818,"order":2819,"visible":24,"navigation":24,"sidebar":24},"oos-controller","OOS Controller",50,78,{"path_key":2821,"parent_path":2816,"product":2816,"title":2822,"product_order":4,"order":2823,"visible":24,"navigation":24,"sidebar":24},"oos-controller\u002Fapplication","應用程式管理 (Application)",83,{"path_key":2825,"parent_path":2816,"product":2816,"title":2826,"product_order":4,"order":2827,"visible":24,"navigation":24,"sidebar":24},"oos-controller\u002Fauth-connect","身分驗證連線 (Auth Connect)",89,{"path_key":2829,"parent_path":2816,"product":2816,"title":2830,"product_order":4,"order":2831,"visible":24,"navigation":24,"sidebar":24},"oos-controller\u002Fbackup","系統設定備份與還原 (Backup)",85,{"path_key":2833,"parent_path":2816,"product":2816,"title":2834,"product_order":4,"order":2835,"visible":24,"navigation":24,"sidebar":24},"oos-controller\u002Fclients","用戶端管理 (Clients)",88,{"path_key":2837,"parent_path":2816,"product":2816,"title":2838,"product_order":4,"order":2839,"visible":24,"navigation":24,"sidebar":24},"oos-controller\u002Fdashboard","儀表板",91,{"path_key":2841,"parent_path":2816,"product":2816,"title":2842,"product_order":4,"order":2843,"visible":24,"navigation":24,"sidebar":24},"oos-controller\u002Fdiagnose","網路診斷工具 (Diagnose)",84,{"path_key":2845,"parent_path":2816,"product":2816,"title":2846,"product_order":4,"order":2847,"visible":24,"navigation":24,"sidebar":24},"oos-controller\u002Fgetting-started","開始使用",80,{"path_key":2849,"parent_path":2816,"product":2816,"title":2850,"product_order":4,"order":2851,"visible":24,"navigation":24,"sidebar":24},"oos-controller\u002Finventory","設備清單 (Inventory)",82,{"path_key":2853,"parent_path":2816,"product":2816,"title":2854,"product_order":4,"order":2855,"visible":24,"navigation":24,"sidebar":24},"oos-controller\u002Fkey-features","主要功能",79,{"path_key":2857,"parent_path":2816,"product":2816,"title":2858,"product_order":4,"order":2859,"visible":24,"navigation":24,"sidebar":24},"oos-controller\u002Flicense","授權許可",97,{"path_key":2861,"parent_path":2816,"product":2816,"title":2862,"product_order":4,"order":2863,"visible":24,"navigation":24,"sidebar":24},"oos-controller\u002Flog","日誌",96,{"path_key":2865,"parent_path":2816,"product":2816,"title":2866,"product_order":4,"order":2867,"visible":24,"navigation":24,"sidebar":24},"oos-controller\u002Fmessage","訊息",95,{"path_key":2869,"parent_path":2816,"product":2816,"title":2870,"product_order":4,"order":2871,"visible":24,"navigation":24,"sidebar":24},"oos-controller\u002Fmission","任務與配置精靈 (Mission)",87,{"path_key":2873,"parent_path":2816,"product":2816,"title":2874,"product_order":4,"order":2875,"visible":24,"navigation":24,"sidebar":24},"oos-controller\u002Fnotification","通知設定 (Notification)",86,{"path_key":2877,"parent_path":2816,"product":2816,"title":2878,"product_order":4,"order":2879,"visible":24,"navigation":24,"sidebar":24},"oos-controller\u002Fprovision","供裝",81,{"path_key":2881,"parent_path":2816,"product":2816,"title":2882,"product_order":4,"order":2883,"visible":24,"navigation":24,"sidebar":24},"oos-controller\u002Fschedule","排程",93,{"path_key":2885,"parent_path":2816,"product":2816,"title":2886,"product_order":4,"order":2887,"visible":24,"navigation":24,"sidebar":24},"oos-controller\u002Fsd-wan","軟體定義廣域網路 (SD-WAN)",90,{"path_key":2889,"parent_path":2816,"product":2816,"title":2890,"product_order":4,"order":2891,"visible":24,"navigation":24,"sidebar":24},"oos-controller\u002Fsecurity","安全性",99,{"path_key":2893,"parent_path":2816,"product":2816,"title":2894,"product_order":4,"order":2895,"visible":24,"navigation":24,"sidebar":24},"oos-controller\u002Fsetting","系統設定",98,{"path_key":2897,"parent_path":2816,"product":2816,"title":2898,"product_order":4,"order":2899,"visible":24,"navigation":24,"sidebar":24},"oos-controller\u002Fstatistics","統計數據",92,{"path_key":2901,"parent_path":2816,"product":2816,"title":2902,"product_order":4,"order":2903,"visible":24,"navigation":24,"sidebar":24},"oos-controller\u002Ftodo","待辦事項",94,{"path_key":2905,"parent_path":2811,"product":2811,"title":2906,"product_order":4,"order":2907,"visible":24,"navigation":24,"sidebar":24},"oos\u002Fappendix-glossary","附錄：詞彙表",77,{"path_key":2909,"parent_path":2811,"product":2811,"title":2910,"product_order":4,"order":2818,"visible":24,"navigation":6,"sidebar":24},"oos\u002Fapplication","應用程式",{"path_key":2912,"parent_path":2909,"product":2811,"title":2913,"product_order":4,"order":2914,"visible":24,"navigation":24,"sidebar":24},"oos\u002Fapplication\u002Fadd-container-template","新增 Container 範本",54,{"path_key":2916,"parent_path":2909,"product":2811,"title":2917,"product_order":4,"order":2918,"visible":24,"navigation":24,"sidebar":24},"oos\u002Fapplication\u002Fadd-hypervisor-template","新增 Hypervisor 範本",53,{"path_key":2920,"parent_path":2909,"product":2811,"title":2921,"product_order":4,"order":2922,"visible":24,"navigation":24,"sidebar":24},"oos\u002Fapplication\u002Fapplication-direct-display-output","應用程式直接顯示輸出",55,{"path_key":2924,"parent_path":2909,"product":2811,"title":2925,"product_order":4,"order":2926,"visible":24,"navigation":24,"sidebar":24},"oos\u002Fapplication\u002Finformation-for-hypervisor-and-container","Hypervisor 與 Container 資訊",52,{"path_key":2928,"parent_path":2909,"product":2811,"title":2929,"product_order":4,"order":2930,"visible":24,"navigation":24,"sidebar":24},"oos\u002Fapplication\u002Finstall-apps","安裝應用程式",51,{"path_key":2932,"parent_path":2909,"product":2811,"title":2933,"product_order":4,"order":2934,"visible":24,"navigation":24,"sidebar":24},"oos\u002Fapplication\u002Fvolume","儲存區 (Volume)",56,{"path_key":2936,"parent_path":2811,"product":2811,"title":2937,"product_order":4,"order":2938,"visible":24,"navigation":6,"sidebar":24},"oos\u002Fdiagnose","診斷",61,{"path_key":2940,"parent_path":2936,"product":2811,"title":2941,"product_order":4,"order":2942,"visible":24,"navigation":24,"sidebar":24},"oos\u002Fdiagnose\u002Fcell-scanner","基地台掃描器",66,{"path_key":2944,"parent_path":2936,"product":2811,"title":2945,"product_order":4,"order":2946,"visible":24,"navigation":24,"sidebar":24},"oos\u002Fdiagnose\u002Fiperf","iPerf",65,{"path_key":2948,"parent_path":2936,"product":2811,"title":2949,"product_order":4,"order":2950,"visible":24,"navigation":24,"sidebar":24},"oos\u002Fdiagnose\u002Fping","Ping",62,{"path_key":2952,"parent_path":2936,"product":2811,"title":2953,"product_order":4,"order":2954,"visible":24,"navigation":24,"sidebar":24},"oos\u002Fdiagnose\u002Fspeedtest","Speedtest",63,{"path_key":2956,"parent_path":2936,"product":2811,"title":2957,"product_order":4,"order":2958,"visible":24,"navigation":24,"sidebar":24},"oos\u002Fdiagnose\u002Ftraceroute","Traceroute",64,{"path_key":2960,"parent_path":2811,"product":2811,"title":2846,"product_order":4,"order":2961,"visible":24,"navigation":6,"sidebar":24},"oos\u002Fgetting-start",23,{"path_key":2963,"parent_path":2960,"product":2811,"title":2964,"product_order":4,"order":2965,"visible":24,"navigation":24,"sidebar":24},"oos\u002Fgetting-start\u002Faccount-management","帳號管理",26,{"path_key":2967,"parent_path":2960,"product":2811,"title":2838,"product_order":4,"order":2968,"visible":24,"navigation":24,"sidebar":24},"oos\u002Fgetting-start\u002Fdashboard",25,{"path_key":2970,"parent_path":2960,"product":2811,"title":2971,"product_order":4,"order":5,"visible":24,"navigation":24,"sidebar":24},"oos\u002Fgetting-start\u002Flogin-to-web-gui","登入 WEB GUI",{"path_key":2973,"parent_path":2811,"product":2811,"title":2974,"product_order":4,"order":2975,"visible":24,"navigation":24,"sidebar":24},"oos\u002Flogs","日誌紀錄",49,{"path_key":2977,"parent_path":2811,"product":2811,"title":2978,"product_order":4,"order":2979,"visible":24,"navigation":6,"sidebar":24},"oos\u002Fnetworking","網路",27,{"path_key":2981,"parent_path":2977,"product":2811,"title":2982,"product_order":4,"order":2983,"visible":24,"navigation":6,"sidebar":24},"oos\u002Fnetworking\u002Fforwarding","轉發",28,{"path_key":2985,"parent_path":2981,"product":2811,"title":2986,"product_order":4,"order":2987,"visible":24,"navigation":24,"sidebar":24},"oos\u002Fnetworking\u002Fforwarding\u002Fport-types","埠類型設定",29,{"path_key":2989,"parent_path":2981,"product":2811,"title":2990,"product_order":4,"order":2991,"visible":24,"navigation":24,"sidebar":24},"oos\u002Fnetworking\u002Fforwarding\u002Fservice-function-chain","服務功能鏈",31,{"path_key":2993,"parent_path":2981,"product":2811,"title":2994,"product_order":4,"order":2995,"visible":24,"navigation":24,"sidebar":24},"oos\u002Fnetworking\u002Fforwarding\u002Fwan-binding","WAN 綁定",30,{"path_key":2997,"parent_path":2977,"product":2811,"title":2998,"product_order":4,"order":2999,"visible":24,"navigation":24,"sidebar":24},"oos\u002Fnetworking\u002Flan","區域網路 (LAN)",45,{"path_key":3001,"parent_path":2997,"product":2811,"title":3002,"product_order":4,"order":3003,"visible":24,"navigation":24,"sidebar":24},"oos\u002Fnetworking\u002Flan\u002Fdhcp-server","DHCP 伺服器 (DHCP Server)",47,{"path_key":3005,"parent_path":2997,"product":2811,"title":3006,"product_order":4,"order":3007,"visible":24,"navigation":24,"sidebar":24},"oos\u002Fnetworking\u002Flan\u002Froute","靜態路由 (Route)",48,{"path_key":3009,"parent_path":2997,"product":2811,"title":3010,"product_order":4,"order":3011,"visible":24,"navigation":24,"sidebar":24},"oos\u002Fnetworking\u002Flan\u002Fvlan","虛擬區域網路 (VLAN)",46,{"path_key":3013,"parent_path":2977,"product":2811,"title":3014,"product_order":4,"order":3015,"visible":24,"navigation":24,"sidebar":24},"oos\u002Fnetworking\u002Fmobile-network","行動網路",32,{"path_key":3017,"parent_path":3013,"product":2811,"title":3018,"product_order":4,"order":3019,"visible":24,"navigation":24,"sidebar":24},"oos\u002Fnetworking\u002Fmobile-network\u002Fapn-edit","APN 編輯",34,{"path_key":3021,"parent_path":3013,"product":2811,"title":3022,"product_order":4,"order":3023,"visible":24,"navigation":24,"sidebar":24},"oos\u002Fnetworking\u002Fmobile-network\u002Fapn-setting","APN 套用與設定",35,{"path_key":3025,"parent_path":3013,"product":2811,"title":3026,"product_order":4,"order":3027,"visible":24,"navigation":24,"sidebar":24},"oos\u002Fnetworking\u002Fmobile-network\u002Fsim-card-binding","SIM 卡綁定",36,{"path_key":3029,"parent_path":3013,"product":2811,"title":3030,"product_order":4,"order":3031,"visible":24,"navigation":24,"sidebar":24},"oos\u002Fnetworking\u002Fmobile-network\u002Fsim-pin","SIM 卡 PIN 碼管理",37,{"path_key":3033,"parent_path":3013,"product":2811,"title":3034,"product_order":4,"order":3035,"visible":24,"navigation":24,"sidebar":24},"oos\u002Fnetworking\u002Fmobile-network\u002Fsim-slot","SIM 卡插槽",33,{"path_key":3037,"parent_path":2977,"product":2811,"title":3038,"product_order":4,"order":3039,"visible":24,"navigation":6,"sidebar":24},"oos\u002Fnetworking\u002Fwan","WAN 廣域網路",41,{"path_key":3041,"parent_path":3037,"product":2811,"title":3042,"product_order":4,"order":3043,"visible":24,"navigation":24,"sidebar":24},"oos\u002Fnetworking\u002Fwan\u002Fmultiple-wan","多重 WAN",42,{"path_key":3045,"parent_path":3037,"product":2811,"title":3046,"product_order":4,"order":3047,"visible":24,"navigation":24,"sidebar":24},"oos\u002Fnetworking\u002Fwan\u002Fnat","NAT 網路位址轉譯",43,{"path_key":3049,"parent_path":3037,"product":2811,"title":3050,"product_order":4,"order":3051,"visible":24,"navigation":24,"sidebar":24},"oos\u002Fnetworking\u002Fwan\u002Fport-forwarding","通訊埠轉發",44,{"path_key":3053,"parent_path":2977,"product":2811,"title":3054,"product_order":4,"order":3055,"visible":24,"navigation":24,"sidebar":24},"oos\u002Fnetworking\u002Fwi-fi","Wi-Fi",38,{"path_key":3057,"parent_path":3053,"product":2811,"title":3058,"product_order":4,"order":2813,"visible":24,"navigation":24,"sidebar":24},"oos\u002Fnetworking\u002Fwi-fi\u002Fportal-mode-with-radius","Portal 模式搭配 RADIUS 驗證",{"path_key":3060,"parent_path":3053,"product":2811,"title":3061,"product_order":4,"order":3062,"visible":24,"navigation":24,"sidebar":24},"oos\u002Fnetworking\u002Fwi-fi\u002Fwi-fi-setting","Wi-Fi 設定",39,{"path_key":3064,"parent_path":2811,"product":2811,"title":3065,"product_order":4,"order":3066,"visible":24,"navigation":24,"sidebar":24},"oos\u002Foos-installation-guide","OOS 安裝指南",22.5,{"path_key":3068,"parent_path":2811,"product":2811,"title":3069,"product_order":4,"order":3070,"visible":24,"navigation":6,"sidebar":24},"oos\u002Fquick-setup-guide","快速設定指南",74,{"path_key":3072,"parent_path":3068,"product":2811,"title":3073,"product_order":4,"order":3074,"visible":24,"navigation":24,"sidebar":24},"oos\u002Fquick-setup-guide\u002Factive-active-wan","雙活 WAN",76,{"path_key":3076,"parent_path":3068,"product":2811,"title":3077,"product_order":4,"order":3078,"visible":24,"navigation":24,"sidebar":24},"oos\u002Fquick-setup-guide\u002Factive-backup-wan","主備 WAN",75,{"path_key":3080,"parent_path":2811,"product":2811,"title":3081,"product_order":4,"order":3082,"visible":24,"navigation":6,"sidebar":24},"oos\u002Fsecurity","資安維護",57,{"path_key":3084,"parent_path":3080,"product":2811,"title":3085,"product_order":4,"order":2798,"visible":24,"navigation":24,"sidebar":24},"oos\u002Fsecurity\u002Faccess-control","存取控制",{"path_key":3087,"parent_path":3080,"product":2811,"title":3088,"product_order":4,"order":3089,"visible":24,"navigation":24,"sidebar":24},"oos\u002Fsecurity\u002Fauthentication","身份驗證",58,{"path_key":3091,"parent_path":3080,"product":2811,"title":3092,"product_order":4,"order":3093,"visible":24,"navigation":24,"sidebar":24},"oos\u002Fsecurity\u002Ffirewall","防火牆",59,{"path_key":3095,"parent_path":2811,"product":2811,"title":3096,"product_order":4,"order":3097,"visible":24,"navigation":6,"sidebar":24},"oos\u002Fsetting","設定",68,{"path_key":3099,"parent_path":3095,"product":2811,"title":3100,"product_order":4,"order":3101,"visible":24,"navigation":24,"sidebar":24},"oos\u002Fsetting\u002Falert","警示",70,{"path_key":3103,"parent_path":3095,"product":2811,"title":3104,"product_order":4,"order":3105,"visible":24,"navigation":24,"sidebar":24},"oos\u002Fsetting\u002Fgeneral","通用設定 (General)",69,{"path_key":3107,"parent_path":3095,"product":2811,"title":3108,"product_order":4,"order":3109,"visible":24,"navigation":24,"sidebar":24},"oos\u002Fsetting\u002Fiscsi-initiator","iSCSI Initiator 發起者",72,{"path_key":3111,"parent_path":3095,"product":2811,"title":3112,"product_order":4,"order":3113,"visible":24,"navigation":24,"sidebar":24},"oos\u002Fsetting\u002Fsnmp","SNMP 網路管理",71,{"path_key":3115,"parent_path":3095,"product":2811,"title":3116,"product_order":4,"order":3117,"visible":24,"navigation":24,"sidebar":24},"oos\u002Fsetting\u002Fsupport","支援",73,{"path_key":3119,"parent_path":2811,"product":2811,"title":3120,"product_order":4,"order":3121,"visible":24,"navigation":24,"sidebar":24},"oos\u002Ftroubleshooting-guide","疑難排解",101,{"path_key":3123,"parent_path":3119,"product":2811,"title":3124,"product_order":4,"order":3125,"visible":24,"navigation":24,"sidebar":24},"oos\u002Ftroubleshooting-guide\u002Fethernet-lan-issues","乙太網路與 LAN 問題",104,{"path_key":3127,"parent_path":3119,"product":2811,"title":3128,"product_order":4,"order":3129,"visible":24,"navigation":24,"sidebar":24},"oos\u002Ftroubleshooting-guide\u002Fmobile-connectivity","行動網路連線",102,{"path_key":3131,"parent_path":3119,"product":2811,"title":3132,"product_order":4,"order":3133,"visible":24,"navigation":24,"sidebar":24},"oos\u002Ftroubleshooting-guide\u002Fwebsite-access","網站存取",106,{"path_key":3135,"parent_path":3119,"product":2811,"title":3136,"product_order":4,"order":3137,"visible":24,"navigation":24,"sidebar":24},"oos\u002Ftroubleshooting-guide\u002Fwifi-connectivity","Wi-Fi 連線",105,{"path_key":3139,"parent_path":2758,"product":3139,"title":3140,"product_order":3141,"order":3142,"visible":24,"navigation":24,"sidebar":24},"orpheagent","OrpheAgent",20,10,{"path_key":3144,"parent_path":3139,"product":3139,"title":3145,"product_order":4,"order":3146,"visible":24,"navigation":24,"sidebar":24},"orpheagent\u002Fapi-endpoints","API 端點",17,{"path_key":3148,"parent_path":3139,"product":3139,"title":3149,"product_order":4,"order":3150,"visible":24,"navigation":24,"sidebar":24},"orpheagent\u002Fcli-commands","CLI 指令",16,{"path_key":3152,"parent_path":3139,"product":3139,"title":3153,"product_order":4,"order":3154,"visible":24,"navigation":24,"sidebar":24},"orpheagent\u002Fdesktop","桌面版",12,{"path_key":3156,"parent_path":3139,"product":3139,"title":3157,"product_order":4,"order":3158,"visible":24,"navigation":24,"sidebar":24},"orpheagent\u002Fdocker","Docker",14,{"path_key":3160,"parent_path":3139,"product":3139,"title":3161,"product_order":4,"order":3162,"visible":24,"navigation":24,"sidebar":24},"orpheagent\u002Flinux-deb","Linux (DEB)",13,{"path_key":3164,"parent_path":3139,"product":3139,"title":3165,"product_order":4,"order":3166,"visible":24,"navigation":24,"sidebar":24},"orpheagent\u002Fopenwrt","OpenWrt",15,{"path_key":3168,"parent_path":3139,"product":3139,"title":3169,"product_order":4,"order":3170,"visible":24,"navigation":24,"sidebar":24},"orpheagent\u002Fphone","手機",12.5,{"path_key":3172,"parent_path":2758,"product":3172,"title":3173,"product_order":2995,"order":3174,"visible":24,"navigation":24,"sidebar":24},"orpheconsole","OrpheConsole",18,{"path_key":3176,"parent_path":3172,"product":3172,"title":3177,"product_order":4,"order":3178,"visible":24,"navigation":24,"sidebar":24},"orpheconsole\u002Forpheconsole-installation","安裝指南",19,{"path_key":3180,"parent_path":3172,"product":3172,"title":3181,"product_order":4,"order":3141,"visible":24,"navigation":24,"sidebar":24},"orpheconsole\u002Forpheconsole-provisioning","供裝指南",{"path_key":3183,"parent_path":3172,"product":3172,"title":3184,"product_order":4,"order":3185,"visible":24,"navigation":24,"sidebar":24},"orpheconsole\u002Forpheconsole-quick-examples","快速範例",21,{"path_key":2802,"parent_path":2758,"product":2802,"title":405,"product_order":3142,"order":3187,"visible":24,"navigation":24,"sidebar":24},1,{"path_key":3189,"parent_path":2802,"product":2802,"title":2846,"product_order":4,"order":1898,"visible":24,"navigation":24,"sidebar":24},"orphelink\u002Fgetting-started",{"path_key":3191,"parent_path":2802,"product":2802,"title":2850,"product_order":4,"order":1926,"visible":24,"navigation":6,"sidebar":24},"orphelink\u002Finventory",{"path_key":3193,"parent_path":3191,"product":2802,"title":3194,"product_order":4,"order":3141,"visible":24,"navigation":24,"sidebar":24},"orphelink\u002Finventory\u002Fauth-device","Device Auth 設備認證",{"path_key":3196,"parent_path":3191,"product":2802,"title":2850,"product_order":4,"order":3142,"visible":24,"navigation":24,"sidebar":24},"orphelink\u002Finventory\u002Finventory",{"path_key":3198,"parent_path":2802,"product":2802,"title":2862,"product_order":4,"order":3199,"visible":24,"navigation":24,"sidebar":24},"orphelink\u002Flog",7,{"path_key":2799,"parent_path":2802,"product":2802,"title":3201,"product_order":4,"order":3202,"visible":24,"navigation":6,"sidebar":24},"OrpheLink 設定",6,{"path_key":2801,"parent_path":2799,"product":2802,"title":33,"product_order":4,"order":2798,"visible":24,"navigation":24,"sidebar":24},{"path_key":3205,"parent_path":2799,"product":2802,"title":3206,"product_order":4,"order":2818,"visible":24,"navigation":24,"sidebar":24},"orphelink\u002Forphelink-setting\u002Ftemplate","範本（Templates）",{"path_key":3208,"parent_path":2799,"product":2802,"title":3209,"product_order":4,"order":3142,"visible":24,"navigation":24,"sidebar":24},"orphelink\u002Forphelink-setting\u002Ftopology","拓撲架構",{"path_key":3211,"parent_path":2802,"product":2802,"title":3212,"product_order":4,"order":2208,"visible":24,"navigation":24,"sidebar":24},"orphelink\u002Fprovision","設備供裝 (Provision)",{"path_key":3214,"parent_path":2802,"product":2802,"title":3096,"product_order":4,"order":3215,"visible":24,"navigation":24,"sidebar":24},"orphelink\u002Fsetting",9,{"left":4,"top":4,"width":5,"height":5,"rotate":4,"vFlip":6,"hFlip":6,"body":3217},"\u003Cg fill=\"none\" stroke=\"currentColor\" stroke-linecap=\"round\" stroke-linejoin=\"round\" stroke-width=\"2\">\u003Crect width=\"18\" height=\"18\" x=\"3\" y=\"3\" rx=\"2\"\u002F>\u003Cpath d=\"M9 3v18\"\u002F>\u003C\u002Fg>",{"left":4,"top":4,"width":5,"height":5,"rotate":4,"vFlip":6,"hFlip":6,"body":3219},"\u003Cg fill=\"none\" stroke=\"currentColor\" stroke-linecap=\"round\" stroke-linejoin=\"round\" stroke-width=\"2\">\u003Cpath d=\"m21 21l-4.34-4.34\"\u002F>\u003Ccircle cx=\"11\" cy=\"11\" r=\"8\"\u002F>\u003C\u002Fg>",{"left":4,"top":4,"width":5,"height":5,"rotate":4,"vFlip":6,"hFlip":6,"body":3221},"\u003Cpath fill=\"none\" stroke=\"currentColor\" stroke-linecap=\"round\" stroke-linejoin=\"round\" stroke-width=\"2\" d=\"m9 18l6-6l-6-6\"\u002F>",{"left":4,"top":4,"width":5,"height":5,"rotate":4,"vFlip":6,"hFlip":6,"body":3223},"\u003Cpath fill=\"none\" stroke=\"currentColor\" stroke-linecap=\"round\" stroke-linejoin=\"round\" stroke-width=\"2\" d=\"m12 19l-7-7l7-7m7 7H5\"\u002F>",{"left":4,"top":4,"width":5,"height":5,"rotate":4,"vFlip":6,"hFlip":6,"body":3225},"\u003Cpath fill=\"none\" stroke=\"currentColor\" stroke-linecap=\"round\" stroke-linejoin=\"round\" stroke-width=\"2\" d=\"M5 12h14m-7-7l7 7l-7 7\"\u002F>",1794471904341]