mirror of
https://github.com/Termix-SSH/Termix.git
synced 2026-10-31 15:45:23 +00:00
Luke GustafsonandZacharyZcR
6b708106e1
* fix(sso): send the PKCE verifier for GitHub login (#1534) * fix(remote-desktop): clip cursor overflow without disabling zoom (#1535) * test(remote-desktop): preserve sessions beyond one hour (#1536) * fix(hosts): expose controls for overflowing editor tabs (#1537) * fix(hosts): expose controls for overflowing editor tabs * test(hosts): mock resize observation in admin panel tests * fix(status): skip TCP probes while host sessions are active (#1538) * fix(database): batch session activity persistence (#1539) * docs(api): describe cookie and API key authentication (#1540) * fix(snippets): repair missing note column on SQLite upgrades (#1541) * fix(docker): retain stored SSH credential association (#1543) * fix(file-manager): render transfer toasts without plugin hooks (#1546) * feat(hosts): keep compact row actions inline (#1547) * fix(auth): allow retrying unavailable second-factor interfaces (#1549) * fix(auth): reject unresolved legacy identity provisioning (#1550) * fix(desktop): ship the plugin SDK inside Mac App Store builds (#1551) * fix(tmux): pass full session info to the terminal's session picker (#1552) The tmux.sessions service reduced detected sessions to bare names, but the picker reads session.name, so every entry rendered blank and selecting one sent an empty name, which created a new session instead of attaching. * fix(ssh): read force keyboard-interactive as a boolean when resolving hosts (#1553) The column holds the text "true"/"false", and the resolver passed it through as-is. The string "false" is truthy, so the password provider treated every saved host as forced keyboard-interactive and left the password out. Jump hops are built straight from the resolved host, so a password hop whose server doesn't offer keyboard-interactive failed with "All configured authentication methods failed". * fix(database): batch database saves for bulk host writes (#1554) * fix(database): yield to the event loop between database saves Each SQLite save serializes and encrypts the whole database into new buffers, which V8 only releases once the event loop turns. Boot migrations and bulk host import write plugin settings per host and per key in an awaited loop, so hundreds of full copies piled up and the container ran out of memory. * fix(database): save once per bulk host write instead of once per row On SQLite every repository write force-saves the whole database. Boot plugin data migrations, host defaults materialization and the bulk host routes write one row per host per setting, so they serialized and encrypted the full database hundreds of times in a row. DatabaseSaveTrigger.batched wraps a function so force saves made while it runs collapse into a single save when it finishes. Nested scopes fold into the outer one, and work that outlives its scope saves normally. * feat(hosts): add instance-wide predefined tag suggestions (#1548) * feat(hosts): add shared predefined tag suggestions * style(hosts): format tag catalog routes * test(database): advance fake timers past the save yield (#1555) * fix(i18n): complete Simplified Chinese core and plugin translations (#1542) * fix(i18n): complete Chinese onboarding and navigation labels * fix(i18n): translate remaining Chinese core and plugin interfaces * fix(i18n): translate host editor tab overflow controls * fix(i18n): use consistent Chinese fleet terminology * fix(i18n): localize hardcoded controls and plugin views * fix(i18n): translate built-in homepage widget catalog * test(homepage): follow translated timezone placeholder * fix(i18n): translate plugin-provided homepage widgets * fix(i18n): localize feature settings section titles * fix: 2.8 oidc accounts unable to sign in after upgrading (#1381) * fix: plugins losing the saved ssh login when copying a host (#1391) * fix: fleets, proxmox and automations not getting the host sudo password * fix: host imports running a defaults pass and metrics restart per host (#1384) * fix: high cpu from status probes and full database saves on every sample (#1300) * fix: user data export freezing the server (#1393) * fix: op:// secret references rejected as ssh keys on credentials (#1394) * fix: slow file deletes from the trash lookups on every delete (#1390) * fix: add openapi docs and error handling to host tag routes * test: compare download stream buffers directly so it stops timing out * chore: drop em dash from host row comment * chore: update release notes for 2.9.1 * fix: restore space to add host tags and redesign predefined tags editor * fix: host key silently accepted when the host is missing from the database (#1397) * fix: clearer host login failed status label and fix its translations (#1396) * chore: add host key and status label fixes to release notes * fix: sso and ldap provider dialogs overflowing the screen and using mismatched toggles * chore: increment ver * fix(audit): store plugin entries with no acting user as a null user_id (#1556) Plugin audit entries written outside a request used the literal "system" as user_id. That column references users.id, so the insert was refused (Postgres logs it as an FK violation) and the entry was silently dropped. Write null instead and keep "system" / plugin:<id> in username. * chore: add sso/ldap dialog and audit log fixes to release notes * fix: tunnels and host settings missing from shared hosts on desktop * fix: remote desktop logins missing from shared hosts on desktop * fix: simplify host status to online/offline and keep it live without a refresh * chore: sync Crowdin translations for 2.9.1 --------- Co-authored-by: ZacharyZcR <zacharyzcr1984@gmail.com>
75 lines
3.1 KiB
JSON
75 lines
3.1 KiB
JSON
{
|
|
"loginWithSso": "使用 SSO 登入",
|
|
"loginWithProvider": "使用 {{name}} 登入",
|
|
"loading": "載入中...",
|
|
"permissions": {
|
|
"manage": {
|
|
"title": "管理 SSO 提供者",
|
|
"description": "新增、變更和刪除使用者可用於登入的 SSO 提供者。"
|
|
}
|
|
},
|
|
"providers": {
|
|
"docsLink": "檢視文件",
|
|
"none": "尚未設定 SSO 提供者。",
|
|
"add": "新增提供者",
|
|
"edit": "編輯提供者",
|
|
"delete": "刪除提供者",
|
|
"deleteConfirm": "刪除此提供者？相關使用者將無法登入。",
|
|
"name": "顯示名稱",
|
|
"namePlaceholder": "我的 SSO 提供者",
|
|
"nameRequired": "必須填寫顯示名稱。",
|
|
"type": "提供者類型",
|
|
"enabled": "已啟用",
|
|
"enabledDesc": "Show a sign in button for this provider on the login screen.",
|
|
"dialogDesc": "Connect an identity provider so users can sign in with it.",
|
|
"sectionGeneral": "General",
|
|
"sectionCredentials": "Client",
|
|
"sectionClaims": "Claims",
|
|
"sectionAccess": "Access",
|
|
"save": "儲存提供者",
|
|
"saving": "儲存中…",
|
|
"saved": "已儲存",
|
|
"saveFailed": "儲存失敗",
|
|
"deleted": "已刪除",
|
|
"deleteFailed": "刪除失敗",
|
|
"loadFailed": "載入 SSO 提供者失敗",
|
|
"cancel": "取消",
|
|
"copy": "複製",
|
|
"copied": "已複製",
|
|
"redirectUri": "重定向 URI",
|
|
"redirectUriDesc": "將此 URL 註冊為身分提供者中的重新導向或回調 URL。",
|
|
"legacyCallback": "保留舊的重定向 URI",
|
|
"legacyCallbackDesc": "此身分提供者是在 Termix 2.9 版本之前設定的，目前仍使用舊的重定向 URI，該 URI 仍然有效。若要遷移到新的重定向 URI，請先在身分提供者中新增 {{uri}} ，然後再將其關閉。",
|
|
"authorizationUrl": "授權網址： {{url}}"
|
|
},
|
|
"fields": {
|
|
"clientId": "用戶端 ID",
|
|
"clientSecret": "用戶端密鑰",
|
|
"secretKeep": "一個秘密被保守。留空即可保密。",
|
|
"issuerUrl": "發行者 URL",
|
|
"authUrl": "授權 URL",
|
|
"tokenUrl": "權杖 URL",
|
|
"userIdentifier": "使用者識別碼路徑",
|
|
"displayName": "顯示名稱路徑",
|
|
"scopes": "範圍",
|
|
"userinfoUrl": "覆寫使用者資訊 URL",
|
|
"groupClaim": "群組宣告",
|
|
"groupClaimDesc": "選用。包含使用者群組的宣告路徑。預設為 groups、roles、group。用於自訂宣告的提供者（例如 Zitadel）。",
|
|
"allowedUsers": "允許的使用者",
|
|
"allowedUsersDesc": "每行一個電子郵件。留空以允許全部。",
|
|
"adminGroup": "管理員群組",
|
|
"adminGroupDesc": "此群組中的使用者將被授予管理員權限。留空以停用群組同步。",
|
|
"caCert": "自訂 CA 憑證",
|
|
"caCertDesc": "選用。PEM 編碼的 CA 憑證，用於使用私有或自簽 CA 的 OIDC 提供者。留空以使用系統信任儲存區。"
|
|
},
|
|
"settings": {
|
|
"silentLoginDefault": {
|
|
"label": "使用 SSO 自動登入",
|
|
"description": "將訪客直接引導至第一個單一登入 (SSO) 供應商，而不是顯示登入表單。環境變數 OIDC_SILENT_LOGIN_DEFAULT 會覆寫此設定。"
|
|
}
|
|
},
|
|
"plugin": {
|
|
"name": "Single sign-on"
|
|
}
|
|
}
|