Skip to content

Releases: hashicorp/boundary

v0.7.5

17 Feb 19:31
a2dc9df
Compare
Choose a tag to compare

0.7.5 (2022/02/17)

New and Improved

  • cli: Update authentication examples to remove password flag and make
    subcommend selection a bit clearer
    (PR)
  • Data Warehouse: Add addresses on plugin based hosts to the database warehouse.
    3 new dimension tables have been added including wh_network_address_group
    (which is now referenced by wh_host_dimension),
    wh_network_address_dimension, and wh_network_address_group_membership.
    (PR)
  • ui: Add support for dynamic host catalog. AWS and Azure plugin-based CRUD operations.

Bug Fixes

  • targets: Specifying a plugin based host id when authorizing a session
    now works. (PR)
  • targets: DNS names are now properly parsed when selecting an endpoint
    for authorizing a session.
    (PR)
  • hosts: Static hosts now include the host sets they are in.
    (PR)

v0.7.4

18 Jan 19:46
Compare
Choose a tag to compare

0.7.4 (2022/01/18)

Deprecations/Changes

  • In newly-created scopes, if default role creation is not disabled, the roles
    will now contain a grant to allow listing targets. This will still be subject
    to listing visibility rules, so only targets the user is granted some action
    on (such as authorize-session) will be returned.

New and Improved

  • config: The description field for workers now supports being set
    from environment variables or a file on disk
    (PR)
  • config: The max_open_connections field for the database field in controllers now supports being set
    from environment variables or a file on disk
    (PR)
  • config: The execution_dir field for plugins now supports being set from environment variables
    or a file on disk.(PR)
  • config: Add support for reading worker controllers off of environment
    variables as well as files. (PR)
  • config: The description field for controllers now supports being set
    from environment variables or a file on disk
    (PR)
  • config: Add support for reading worker tags off of environment variables
    as well as files. (PR)
  • config: Add support for go-sockaddr templates to Worker and Controller
    addresses. (PR)
  • controllers/workers: Add client IP to inbound request information which is included in
    Boundary events (PR)
  • host: Plugin-based host catalogs will now schedule updates for all
    of its host sets when its attributes are updated.
    (PR)
  • scopes: Default roles in newly-created scopes now contain a grant to allow
    listing targets. (PR)
  • plugins/aws: AWS plugin based hosts now include DNS names in addition to the
    IP addresses they already provide.

Bug Fixes

  • session: Fix duplicate sessions and invalid session state transitions. (PR)

v0.7.3

16 Dec 17:39
Compare
Choose a tag to compare

0.7.3 (2021/12/16)

Bug Fixes

  • target: Fix permission bug which prevents the UI from being able to add and remove
    host sources on a target. (PR)
  • credential: Fix panic during credential issue when a nil secret is received. This can
    occur when using the Vault KV backend which returns a nil secret and no error if the
    secret does not exist. (PR)

v0.7.2

15 Dec 22:05
Compare
Choose a tag to compare

0.7.2 (2021/12/14)

Security

  • Boundary now uses Go 1.17.5 to address a security vulnerability (CVE-2021-44716) where
    an attacker can cause unbounded memory growth in a Go server accepting HTTP/2 requests.
    See the Go announcement for
    more details. (PR)

v0.7.1

19 Nov 03:16
Compare
Choose a tag to compare

0.7.1 (2021/11/18)

Bug Fixes

  • db: Fix panic invoking the CLI on Windows. Some changes to how the binary is
    initialized resulted in running some functions on every startup that looked
    for some embedded files. However, Go's embed package does not use OS-specific
    path separators, so a mismatch between path separators caused a failure in the
    function. (PR)

v0.7.0

17 Nov 22:52
18de365
Compare
Choose a tag to compare

0.7.0 (2021/11/17)

Deprecations/Changes

  • tls: Boundary's support for TLS 1.0/1.1 on the API listener was broken. Rather
    than fix this, we are simply not supporting TLS 1.0/1.1 as they are insecure.

New and Improved

  • Boundary now supports dynamic discovery of host resources using our (currently
    internal) new plugin system. See the
    documentation for configuration
    instructions. Currently, only Azure and AWS are supported, but more providers
    will be following in future releases.
  • workers: The existing worker connection replay prevention logic has been
    enhanced to be more robust against attackers that have decryption access to
    the shared worker-auth KMS key
    (PR)

Bug Fixes

  • tls: Support TLS 1.2 for more clients. This was broken for some clients due to
    a missing mandated cipher suite of the HTTP/2 (h2) specification that could
    result in no shared cipher suites between the Boundary API listener and those
    clients. (PR)
  • vault: Fix credential store support when using Vault namespaces
    (Issue,
    PR)

v0.6.2

28 Sep 18:54
Compare
Choose a tag to compare

0.6.2 (2021/09/27)

Deprecations/Changes

  • permissions: Fix bug in Host Sets service that authenticated requests
    againist incorrect grant actions. This bug affects the SetHosts, AddHosts
    and RemoveHosts paths that do not have wildcard (*) action grants.
    If affected, please update grant actions as follows:
    • set-host-sets -> set-hosts
    • add-host-sets -> add-hosts
    • remove-host-sets -> remove-hosts
      (PR).
  • Removes support for the auth-methods/<id>:authenticate:login action that was
    deprecated in Boundary 0.2.0, please use
    auth-methods/<id>:authenticate instead.
    (PR).
  • Removes support for the credential field within auth-methods/<id>:authenticate
    action. This field was deprecated in Boundary 0.2.0, please use
    attributes instead.
    (PR).

v0.6.1

15 Sep 22:11
1f7999e
Compare
Choose a tag to compare

0.6.1 (2021/09/14)

Bug Fixes

  • grants: Fix issue where credential-store, credential-library, and
    managed-group would not be accepted as specific type values in grant
    strings. Also, fix authorized actions not showing credential-store values in
    project scope output. (PR)
  • actions: Fix sessions collection actions not being visible when reading a
    scope (PR)
  • credential stores: Fix credential stores not showing authorized collection
    actions (PR)

v0.6.0

09 Sep 11:08
7746916
Compare
Choose a tag to compare

0.6.0 (2021/09/03)

New and Improved

  • ui: Reflect user authorized actions in the UI: users now see only actionable
    items for which they have permissions granted.
  • ui: Icons refreshed for a friendlier look and feel.

Bug Fixes

  • controller: Fix issue with recursive listing across services when using the
    unauthenticated user (u_anon) with no token and the list was started in a
    scope where the user does not have permission
    (PR)
  • grants: Fix grant format type=<type>;output_fields=<fields> with no action
    specified. In some code paths this format would trigger an error when
    validating even though it is correctly handled within the ACL code.
    (PR)
  • targets: Fix panic when using boundary targets authorize-session
    (issue,
    PR).

v0.5.1

19 Aug 17:54
5f88243
Compare
Choose a tag to compare

0.5.1 (2021/08/16)

New and Improved

  • Data Warehouse: Add OIDC auth method and accounts to the database warehouse.
    Four new columns have been added to the wh_user_dimension table:
    auth_method_external_id, auth_account_external_id,
    auth_account_full_name, and auth_account_email.
    (PR)

Bug Fixes

  • events: Fix panic when using the hclog-text event's format.
    (PR)
  • oidc managed groups: Allow colons in selector paths
    (PR)