mirror of
https://github.com/Termix-SSH/Termix.git
synced 2026-10-30 15:15:24 +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.6 KiB
JSON
75 lines
3.6 KiB
JSON
{
|
|
"loginWithSso": "Entrar com SSO",
|
|
"loginWithProvider": "Faça login com {{name}}",
|
|
"loading": "Carregando...",
|
|
"permissions": {
|
|
"manage": {
|
|
"title": "Gerenciar provedores de SSO",
|
|
"description": "Adicione, altere e remova os provedores de SSO que os usuários podem usar para fazer login."
|
|
}
|
|
},
|
|
"providers": {
|
|
"docsLink": "Documentação",
|
|
"none": "Nenhum provedor de SSO configurado.",
|
|
"add": "Adicionar provedor",
|
|
"edit": "Editar provedor",
|
|
"delete": "Excluir provedor",
|
|
"deleteConfirm": "Excluir este provedor? Os usuários associados não poderão fazer login.",
|
|
"name": "Nome de exibição",
|
|
"namePlaceholder": "Meu provedor de SSO",
|
|
"nameRequired": "É necessário um nome de exibição.",
|
|
"type": "Tipo de provedor",
|
|
"enabled": "Habilitado",
|
|
"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": "Salvar provedor",
|
|
"saving": "Salvando...",
|
|
"saved": "Salvo",
|
|
"saveFailed": "Falha ao salvar",
|
|
"deleted": "Apagado",
|
|
"deleteFailed": "Falha ao apagar",
|
|
"loadFailed": "Falha ao carregar os provedores de SSO",
|
|
"cancel": "Cancelar",
|
|
"copy": "Copiar",
|
|
"copied": "Copiado",
|
|
"redirectUri": "URI de redirecionamento",
|
|
"redirectUriDesc": "Registre este URL como URL de redirecionamento ou de retorno de chamada em seu provedor de identidade.",
|
|
"legacyCallback": "Mantenha o URI de redirecionamento antigo.",
|
|
"legacyCallbackDesc": "Este provedor foi configurado antes do Termix 2.9 e ainda usa o URI de redirecionamento antigo, que continua funcionando. Para migrar para o novo, adicione {{uri}} no seu provedor de identidade primeiro e depois desative-o.",
|
|
"authorizationUrl": "URL de autorização: {{url}}"
|
|
},
|
|
"fields": {
|
|
"clientId": "ID do cliente",
|
|
"clientSecret": "Segredo do cliente",
|
|
"secretKeep": "Um segredo foi guardado. Deixe este campo vazio para mantê-lo.",
|
|
"issuerUrl": "URL do emissor",
|
|
"authUrl": "URL de autorização",
|
|
"tokenUrl": "URL do token",
|
|
"userIdentifier": "Caminho do identificador do usuário",
|
|
"displayName": "Nome de exibição Caminho",
|
|
"scopes": "Escopos",
|
|
"userinfoUrl": "Substituir URL de informações do usuário",
|
|
"groupClaim": "Reivindicação de grupo",
|
|
"groupClaimDesc": "Opcional. O caminho da declaração que contém os grupos do usuário. O padrão é grupos, funções e, em seguida, grupo. Use isso para provedores com uma declaração personalizada (por exemplo, Zitadel).",
|
|
"allowedUsers": "Usuários autorizados",
|
|
"allowedUsersDesc": "Um e-mail por linha. Deixe em branco para permitir todos.",
|
|
"adminGroup": "Grupo de Administração",
|
|
"adminGroupDesc": "Os usuários deste grupo têm privilégios de administrador. Deixe em branco para desativar a sincronização do grupo.",
|
|
"caCert": "Certificado CA personalizado",
|
|
"caCertDesc": "Opcional. Certificado CA codificado em PEM para provedores OIDC que utilizam uma CA privada ou autoassinada. Deixe em branco para usar o repositório de certificados confiáveis do sistema."
|
|
},
|
|
"settings": {
|
|
"silentLoginDefault": {
|
|
"label": "Faça login automaticamente com SSO.",
|
|
"description": "Direcione os visitantes diretamente para o primeiro provedor de SSO em vez de exibir o formulário de login. A variável de ambiente OIDC_SILENT_LOGIN_DEFAULT substitui essa configuração."
|
|
}
|
|
},
|
|
"plugin": {
|
|
"name": "Single sign-on"
|
|
}
|
|
}
|