Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Bump version for v1.14.1+suite.1 release #237

Merged
merged 1 commit into from
Nov 15, 2021
Merged

Bump version for v1.14.1+suite.1 release #237

merged 1 commit into from
Nov 15, 2021

Conversation

jtuttle
Copy link
Member

@jtuttle jtuttle commented Nov 12, 2021 •
edited
Loading

Release Notes

All notable changes to this project will be documented in this file.

[1.14.1+suite.1] - 2021-11-12

Table of Contents

Components

These are the components that combine to create this Conjur OSS Suite release and links
to their releases:

Conjur Server

Conjur SDK

Platform Integrations

DevOps Tools

Secretless Broker

Summon

Installation Instructions for the Suite Release Version of Conjur

Installing the Suite Release Version of Conjur requires setting the container image tag. Below are more specific instructions depending on environment.

  • Docker or docker-compose

    Set the container image tag to cyberark/conjur:1.14.1.
    For example, make the following update to the conjur service in the quickstart docker-compose.yml

    image: cyberark/conjur:1.14.1

  • Conjur Open Source Helm chart

    Update the image.tag value and use the appropriate release of the helm chart:

    helm install ... \
  --set image.tag="1.14.1" \
  ...
  https://github.com/cyberark/conjur-oss-helm-chart/releases/download/v2.0.4/conjur-oss-2.0.4.tgz

Upgrade Instructions

Upgrade instructions are available for the following components:

Changes

The following are changes to the constituent components since the last Conjur
OSS Suite release:

cyberark/conjur

v1.14.1 (2021-11-05)

  • Fixed
    • Version bump to resolve build error on tagged master. #2416

v1.14.0 (2021-11-04)

  • Added

    • Create default account when no account is specified in conjurctl account create.
      cyberark/conjur#2388
    • JWT Authenticator supports nested claims in token-app-property, enforced-claims,
      claim-aliases and role annotations. (ONYX-11204:
      #2397,
      #2404,
      #2403)

  • Changed

cyberark/conjur-cli

v6.2.5 (2021-09-29)

cyberark/secrets-provider-for-k8s

v1.1.6 (2021-10-31)

cyberark/secretless-broker

v1.7.8 (2021-11-09)

v1.7.7 (2021-11-03)

  • Fixed

    • Request-signing on the AWS connector was updated to address a bug that was
      causing failed integrity checks, where the request-signing by Secretless was
      incorporating more headers than were used on the original request-signing. The
      fix limits the headers used by Secretless to those used in the original
      request. cyberark/secretless-broker#1432

  • Security

@jtuttle jtuttle requested a review from a team as a code owner November 12, 2021 16:56
@jtuttle
Copy link
Member Author

jtuttle commented Nov 12, 2021 •
edited
Loading

@alexkalish

What's New

This suite release aligned with Conjur Server version 1.14.1. It includes a new way to use the Secrets Provider for Kubernetes.

Push-to-File Mode (Community release)

The Secrets Provider for Kubernetes can now be configured to output secret values to a file that can be accessed through a shared mounted volume. Providing secrets in this manner should require zero application changes, as reading local files is a common, platform agnostic delivery method. See PUSH_TO_FILE.md for more details. This is a community level release.

Nested JWT Claims

The Conjur JWT authenticator now supports claims that contain other, nested claims. This makes the authenticator more flexible and allows it to support a wider range of use-cases.

@jtuttle jtuttle merged commit fecd740 into main Nov 15, 2021
@jtuttle jtuttle deleted the release-v1.14.1+suite.1 branch November 15, 2021 20:34
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@alexkalish alexkalish alexkalish approved these changes

Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
2 participants
@jtuttle @alexkalish