threshold-ui/addons/core/translations/resources/en-us.yaml

# Copyright (c) HashiCorp, Inc.
# SPDX-License-Identifier: MPL-2.0

account:
  title: Account
  title_plural: Accounts
  description: An account allows a user to log into Boundary with a particular auth method. Users may have multiple accounts for different auth methods.
  messages:
    welcome:
      title: Welcome to Accounts
      description: Create and manage accounts for an auth method.
    set-password:
      description: Set a password for the account.
  types:
    password: Password
    oidc: OIDC
  titles:
    new: New Account
  actions:
    create: Create Account
    delete: Delete Account
auth-method:
  title: Auth Method
  title_plural: Auth Methods
  description: Auth methods allow users to authenticate within a scope.
  messages:
    welcome:
      title: Welcome to Auth Methods
      description: Auth methods are configurations to authenticate users.
    none:
      title: No Auth Methods
      description: No auth methods were found for this scope.
    no-primary-auth-method:
      title: 'Recommendation: Select a Primary Auth Method'
      description: A primary auth method auto-creates users when they authenticate for the first time.  Scopes without primary auth methods may experience authentication failures.
    pending:
      title: Authentication Pending
      description: Complete authentication in the newly-opened window.
  titles:
    new: New Auth Method
    new-signing-algorithm: New Signing Algorithm
    new-allowed-audience: New Allowed Audience
    new-claims-scope: New Claims Scope
    new-from-claim: New From Claim
    new-to-claim: New To Claim
    new-certificate: New Certificate
  types:
    password: Password
    oidc: OIDC
  actions:
    create: Create Auth Method
    delete: Delete Auth Method
    make-primary: Make Primary
    remove-as-primary: Remove as Primary
  notifications:
    make-primary-success: Auth method successfully elected to primary.
    remove-as-primary-success: Auth method successfully removed as primary.
  questions:
    make-primary: Make primary auth method?
    remove-as-primary: Remove primary auth method?
    make-primary-confirm: 'A primary auth method auto-creates users on their first authentication attempt if needed.  Note:  if you change the primary auth method, the previous primary will no longer auto-create users.'
    remove-as-primary-confirm: Removing the primary auth method may lead to authentication failures for this scope.
    no-see-window: Don't see the new window?
group:
  title: Group
  title_plural: Groups
  description: Groups are collections of users. Groups may be assigned to roles to receive the role’s grants.
  messages:
    welcome:
      title: Welcome to Groups
    members:
      title: Members
      description: Members are the users assigned to a group.
    add-members:
      title: Add Members
      description: Select users to add users to this group.
    no-members:
      title: No Members Available
      description: There are no members available to add to this group.
  titles:
    new: New Group
  actions:
    add-members: Add Members
    delete: Delete Group
host-catalog:
  title: Host Catalog
  title_plural: Host Catalogs
  description: A host catalog is a collection of hosts and host sets.
  type: Type
  messages:
    welcome:
      title: Welcome to Host Catalogs
  titles:
    new: New Host Catalog
  actions:
    delete: Delete Host Catalog
  help:
    static: Provide a list of hosts and host sets with static addresses
    plugin: Automate discovery of target hosts and services on Azure or AWS
  types:
    static: Static
    unknown: Plugin
    aws: AWS
    azure: Azure
    plugin: Dynamic
  form:
    aws_region:
      label: AWS Region
      help: AWS region of the hosts to be added to the catalog.
    azure_client_id:
      label: Client/Application ID
      help: The client (application) ID of an Azure service principal that Boundary will use to authenticate and discover hosts from Azure.
host-set:
  title: Host Set
  title_plural: Host Sets
  description: A host set is a collection of hosts within a host catalog.
  titles:
    new: New Host Set
  actions:
    add: Add Host Set
    create: New Host Set
    delete: Delete Host Set
    create-and-add-host: Create and Add Host
    add-hosts: Add Existing Host
  form:
    filter:
      label: Filter
      aws:
        help: Create a filter to select resources using values such as tag name or tag value. The AWS filter format is tag:<tag-name>=<tag-value>. For example:tag:application=production
      azure:
        help: Create a filter to select resources using values such as tag name or tag value. The Azure filter format is:tagName eq ‘<tag-name>’ and tagValue eq ‘<tag-value>'. For example:tagName eq 'application' and tagValue eq 'production'
    preferred_endpoints:
      label: Preferred Endpoints
      help: Optional. Preferred address at which the host should be accessed when multiple options are present, in cidr:<valid IPv4/6 CIDR> or dns:<globbed name> format.
  messages:
    welcome:
      title: Welcome to Host Sets
  host:
    messages:
      none:
        title: No Hosts
        description: No hosts available in this host set.
      add:
        title: Add Hosts
        description: Select hosts that belong to this host set.
      add-none:
        title: No Hosts Available
        description: No hosts available for selection.
host:
  title: Host
  title_plural: Hosts
  description: A host is a resource that may be accessed by a Boundary target.
  messages:
    welcome:
      title: Welcome to Hosts
    none:
      title: No Hosts
      description: No hosts available in this scope.
    none-friendly:
      title: No Hosts Available
      description: No hosts available to display yet.
  titles:
    new: New Host
  actions:
    add: Add Host
    create: New Host
    delete: Delete Host
session:
  title: Session
  title_plural: Sessions
  active_plural: Active Sessions
  description: A session is a connection to a target initiated through Boundary.
  status:
    active: Active
    pending: Pending
    canceling: Canceling
    terminated: Terminated
  messages:
    none:
      title: No Sessions
      description: There are no active sessions within the current scope.
    none-friendly:
      title: No Sessions Available
      description: No sessions available to display yet.
    none-active-friendly:
      title: No Active Sessions Available
      description: No active sessions available to display yet.
  actions:
    connect: Connect
  credential:
    title: Credential
    title_plural: Credentials
    secret:
      label: Secret
    credential_source:
      title: Credential Source
    actions:
      raw-api:
        show: View raw API output
        hide: Hide raw API output
org:
  title: Org
  title_plural: Orgs
  description: An org is a type of scope used to organize projects and IAM resources.  Orgs are child scopes of the global scope.
  messages:
    welcome:
      title: Welcome to Orgs
    settings:
      title: Org Settings
  titles:
    new: New Org
  actions:
    delete: Delete Org
project:
  title: Project
  title_plural: Projects
  description: A project is a type of scope used to organize resources such as targets and host catalogs.
  messages:
    welcome:
      title: Welcome to Projects
    settings:
      title: Project Settings
  titles:
    new: New Project
  actions:
    delete: Delete Project
user:
  title: User
  title_plural: Users
  description: Users are entities authorized to access Boundary.  Users may be assigned to roles as principals, thus receiving role grants.
  messages:
    welcome:
      title: Welcome to Users
    accounts:
      title: Accounts
      description: Users may be associated with any number of accounts.
    add-accounts:
      title: Add Accounts
      description: Select accounts to associate with this user.
    no-accounts:
      title: No Accounts Available
      description: There are no accounts available to add to this user.
  titles:
    new: New User
  actions:
    add-accounts: Add Accounts
    delete: Delete User
role:
  title: Role
  title_plural: Roles
  description: Roles are collections of capability grants and the principals (users and groups) assigned to them.
  messages:
    welcome:
      title: Welcome to Roles
  titles:
    new: New Role
  actions:
    create: Create Role
    delete: Delete Role
  principal:
    title: Principal
    title_plural: Principals
    description: Principals are the users and groups assigned to a role and bounded by a role’s grants.
    messages:
      welcome:
        title: Welcome to Principals
        description: Principals are not assigned in this role.
      none:
        title: No Principals Available
        description: Principals are not available for assignment.
      add-principals:
        title: Add Principals
        description: Select users and groups to assign to this role.
    types:
      user: User
      group: Group
      managed-group: Managed Group
    actions:
      add-principals: Add Principals
  grant:
    title: Grant
    title_plural: Grants
    description: Grants are permissions which allow roles to take actions and access resources.
    actions:
      create: New Grant
target:
  title: Target
  title_plural: Targets
  description: A target is a logical collection of host sets which may be used to initiate sessions.
  messages:
    welcome:
      title: Welcome to Targets
    none:
      title: No Targets Available
      description: No Targets to display yet. Contact your Boundary admin if you don't see a Target you expect access to.
    connection-success:
      title: Successfully Connected
    connection-details:
      title: Target Connection Details
    proxy_url:
      title: Proxy URL
  titles:
    new: New Target
  actions:
    create: New Target
    delete: Delete Target
    add-host-sources: Add Host Sources
    add-brokered-credential-sources: Add Brokered Credentials
    add-injected-application-credential-sources: Add Injected Application Credentials
    remove-address: Remove address and save
  types:
    tcp: Generic TCP
    ssh: SSH
  help:
    tcp: Generic TCP supports a broad range of connection types.
    ssh: Protocol-aware SSH with support for credential injection.
  form:
    type:
      label: Type
      help: Target type is the protocol with which end users should connect to this target.  Choose Generic TCP for broad support of common protocols including RDP, K8s, many databases, and more.
    target-address:
      label: Target Address
      help: Must be a valid IP address or DNS name. We recommend leaving this blank and using host catalogs and host sets instead if you want to use this target on multiple hosts.
    worker_filter:
      label: Worker Filter
      help: Deprecated. Boolean expression to filter the workers that are allowed to satisfy this request.
  questions:
    delete-host-sources:
      title: Remove associated host sources?
      message: You have {hostSourceCount, plural, one {# host source} other {# host sources}} associated with this target. Adding an address will remove {hostSourceCount, plural, one {this host source} other {these host sources }} when you save your changes.
  host-source:
    title: Host Source
    title_plural: Host Sources
    messages:
      welcome:
        title: Welcome to Host Sources
        description: No hosts sources in this target.
      none:
        title: No Host Sources Available
        description: No hosts sources available to add to target.
      add:
        title: Add Host Sources
        description: Select host sources to assign to this target.
    questions:
      delete-address:
        title: Remove target address?
        message: This target has an assigned address. Adding a host source will remove the assigned address from the target when you save your changes.
  brokered-credential-source:
    title: Brokered Credential
    title_plural: Brokered Credentials
    messages:
      welcome:
        title: Welcome to brokered credentials
        description: No brokered credential sources in this target.
      none:
        title: No Brokered Credential Sources Available
        description: No brokered credential sources available to add to this target.
      add:
        title: Add Brokered Credential Sources
        description: Select brokered credential sources to assign to this target.
  injected-application-credential-source:
    title: Injected Application Credential
    title_plural: Injected Application Credentials
    messages:
      welcome:
        title: Welcome to Injected Application credentials
        description: No Injected application credential sources in this target.
      none:
        title: No Injected Application Credential Sources Available
        description: No Injected Application credential sources available to add to this target.
      add:
        title: Add Injected Application Credential Sources
        description: Select injected Application credential sources to assign to this target.
  workers:
    title: Workers
    description: You can customize how your workers route traffic to this target by setting up a filter that matches specific worker tags. If your target is in a private network, we recommend setting up an egress filter to specify a worker inside the network so that Boundary can access the host. Ingress and egress filters are allowed to select the same worker.
    deprecation_message:
      title: Worker filters have been updated
      description: This target is configured using an older version of worker filters. You can update to the new filters but this will also update this field in the Boundary API. We will continue to use this filter until you update.
    diagram:
      client: Client
      any-worker: Any worker
      frontline-worker: Frontline worker
      hcp-worker: HCP worker
      egress-worker: Egress worker
      ingress-worker: Ingress worker
      host: Host
      network: Private network
    filter-explainer:
      any-worker: In this configuration, the client will attempt to connect through any client-accessible worker.
      egress-worker: In this configuration, the client will attempt to connect through any filtered egress worker.
      ingress-worker: In this configuration, the client will attempt to connect through any filtered ingress worker.
      hcp-worker: In this configuration, the client will attempt to connect through any HCP-managed worker.
      dual-egress-on: In this configuration, the client will attempt to  connect through any client-accessible "frontline" worker and reach the host through any filtered egress worker.
      dual-egress-on-ingress-on: In this configuration, the client will attempt to connect through any filtered ingress worker and reach the host through any filtered egress worker.
      hcp-dual-egress-on: In this configuration, the client will attempt to connect through any HCP-managed worker and reach the host through any filtered egress worker.
    filter:
      title: Filter
      description: Boolean expression.
    egress_worker_filter:
      title: Egress worker filter
      description: Specify workers that have access to the target (such as within a private network).
    ingress_worker_filter:
      title: Ingress worker filter
      description: Specify workers Boundary should use to start the route to this target.
    actions:
      update-filter: Update Filter
credential-store:
  title: Credential Store
  title_plural: Credential Stores
  description: A credential store is a collection of credentials and credential libraries.
  messages:
    welcome:
      title: Welcome to Credential Stores
  titles:
    new: New Credential Store
  actions:
    delete: Delete Credential Store
  types:
    vault: Vault
    static: Static
  help:
    vault: The host details are brokered by a Vault server.
    static: This host uses static credentials, such as a username and password or key pair.
  form:
    address:
      label: Address
      help: The address of the Vault server. This should be a complete URL such as https://127.0.0.1:8200.
    namespace:
      label: Namespace
      help: A Vault namespace. Requires Vault Enterprise.
    ca_cert:
      label: CA Certificate
      help: A PEM-encoded CA certificate to verify the Vault server's TLS certificate.
    tls_server_name:
      label: TLS Server Name
      help: Name to use as the SNI host when connecting to Vault via TLS.
    tls_skip_verify:
      label: TLS Skip Verify
      help: Disable verification of TLS certificates. Using this option is highly discouraged as it decreases the security of data transmissions to and from the Vault server.
    token:
      label: Token
      help: A token used for accessing Vault.
    token_hmac:
      label: Token HMAC
    client_certificate:
      label: Client Certificate
      help: A PEM-encoded client certificate to use for TLS authentication to the Vault server.
    client_certificate_key:
      label: Client Certificate Key
      help: A PEM-encoded private key matching the client certificate from Client Certificate.
    client_certificate_key_hmac:
      label: Client Certificate Key HMAC
    worker_filter:
      label: Worker Filter
      help: A filter used to control which PKI workers can handle Vault requests, allowing the use of private Vault instances with Boundary.
credential-library:
  title: Credential Library
  title_plural: Credential Libraries
  description: A credential library is a resource that provides credentials.
  titles:
    new: New Credential Library
  actions:
    create: New Credential Library
    delete: Delete Credential Library
  messages:
    none:
      title: No Credential Libraries Available
      description: No Credential Libraries available in this credential store.
  form:
    vault_path:
      label: Vault Path
      help: The path the library uses when requesting credentials from Vault.
    http_method:
      label: HTTP Method
      help: The HTTP method the library uses when requesting credentials from Vault.
    http_request_body:
      label: HTTP Method POST Request Body
      help: The body of the HTTP request the library sends to Vault when requesting credentials. Only allowed when HTTP method is set to POST.
    username:
      label: Username
      help: The username to use when making an SSH connection. This can be templated to use the requesting user's name. This will be included in the valid_principles when making the request to Vault.
    key_type:
      label: Key Type
      help: Specifies the desired key type to use when generating a private key.
    key_bits:
      label: Key Bits
      help: Specifies the number of bits used generating the private key.
    ttl:
      label: TTL
      help: Specifies the Requested Time to Live for the certificate.
    key_id:
      label: Key ID
      help: Specifies the key id that the created certificate should have.
    critical_options:
      label: Critical Options
      help: Specifies a map of the critical options that the certificate should be signed for.
    extensions:
      label: Extensions
      help: Specifies a map of the extensions that the certificate should be signed for.
  types:
    vault-generic: Generic Secrets
    vault-ssh-certificate: SSH Certificates
  help:
    vault-generic: Authorize sessions using credentials brokered by Vault
    vault-ssh-certificate: Authorize sessions using the SSH Secrets Engine in Vault
credential:
  title: Credential
  title_plural: Credentials
  description: Credentials are static resources like usernames and passwords.
  titles:
    new: New Credential
  actions:
    create: New Credential
    delete: Delete Credential
  messages:
    none:
      title: No Credentials Available
      description: No Credentials available in this credential store.
  types:
    username_password: Username & Password
    ssh_private_key: Username & Key Pair
    json: JSON
    unknown: Unknown
  help:
    username_password: Connect using the provided username and password.
    ssh_private_key: Connect using a username, public key, and private key.
    json: Connect using a JSON blob containing the credentials.
  form:
    username:
      label: Username
      help: The username to use when connecting with this credential store.
    password:
      label: Password
      help: The password to use when signing in with this credential store.
    private_key:
      label: SSH Private Key
      help: The private key to use when connecting with this credential store.
    private_key_passphrase:
      label: Passphrase
      help: Optional.
    json:
      label: JSON
      help: This is the JSON blob that provides credentials to the host. After this data is saved, you will not be able to edit it again without replacing it.
scope:
  title: Scope
  title_plural: Scopes
  messages:
    cannot_read: While you do not have permission to read this scope, you may have permission to view resources within it.
managed-group:
  title: Managed Group
  title_plural: Managed Groups
  description: A managed group represents a collection of accounts.
  actions:
    delete: Delete Managed Group
    create: Create Managed Group
  messages:
    welcome:
      title: Welcome to Managed Groups
      description: Create and manage managed groups for an auth method.
  member:
    title: Member
    title_plural: Members
    messages:
      title: Welcome to Members
      description: No members in this managed group.
worker:
  title: Worker
  title_pki: New PKI Worker
  title_plural: Workers
  description: Workers are the server components that perform the session handling.
  actions:
    register: Register Worker
    delete: Remove Worker
  messages:
    welcome:
      title: Welcome to Workers
  table:
    session_count: Session Count
    ip_address: IP Address
    release_version: Release Version
    tag_count: '{tagCount, plural, =1 {# tag} other {# tags}}'
  form:
    cluster_id:
      label: Boundary Cluster ID
      help: The cluster ID is the UUID in the HCP Boundary Controller URL.
    ip_address:
      label: Worker public address
      help: Public IP or address.
    initial_upstreams:
      label: Initial Upstreams
      help: A list of hosts/IP addresses and optionally ports for reaching Boundary cluster.  The port will default to :9201 if not specified.
    config_file_path:
      label: Config file path
      help: The path on your server where you will store your configuration file.
    worker_tags:
      label: Worker Tags
      help: Boundary can use tags to define key-value pairs which targets can use to determine where they should route connections.
    steps:
      1:
        title: 1. Configure your new worker
        create_directory: Create a configuration file in a new directory on your server
        create_config: 'Open the file with a text editor, such as Vi. Paste the following configuration into the worker config file:'
        save_config: Save the configuration in your `pki-worker.hcl` file.
      2:
        title: 2. Install & start Boundary on your server
        run_command: 'Run this command on your server to install Boundary:'
        copy_registration_request: When the server starts, it will print details related to this worker. Copy the value for
      3:
        title: 3. Confirm the worker when they connect
        worker_auth_registration_request:
          label: Worker Auth Registration Request
          help: The registration key provided by this worker when it started
        registered: Registered