2020-05-13 23:55:32 +00:00
|
|
|
---
|
|
|
|
|
layout: docs
|
|
|
|
|
page_title: Upgrading to Vault 1.4.1 - Guides
|
|
|
|
|
description: |-
|
|
|
|
|
This page contains the list of deprecations and important or breaking changes
|
|
|
|
|
for Vault 1.4.1. Please read it carefully.
|
|
|
|
|
---
|
|
|
|
|
|
|
|
|
|
# Overview
|
|
|
|
|
|
|
|
|
|
This page contains the list of deprecations and important or breaking changes
|
|
|
|
|
for Vault 1.4.1 compared to 1.4.0. Please read it carefully.
|
|
|
|
|
|
2023-07-18 21:07:55 +00:00
|
|
|
## AWS auth metadata
|
2020-05-13 23:55:32 +00:00
|
|
|
|
|
|
|
|
The metadata handling for AWS Auth logins has changed:
|
|
|
|
|
|
|
|
|
|
The default set of metadata fields has been changed to `account_id` and `auth_type`. If your
|
|
|
|
|
application relies on fields that were removed, they may be added back via the AWS Auth identity
|
|
|
|
|
configuration endpoint (see example below).
|
|
|
|
|
|
2023-07-18 21:07:55 +00:00
|
|
|
## Known issues
|
2020-05-13 23:55:32 +00:00
|
|
|
|
|
|
|
|
The AWS metadata changes have caused an issue preventing renewal of tokens issued via AWS Auth.
|
2020-05-22 01:51:19 +00:00
|
|
|
This has been fixed in Vault 1.4.2. The issue may be addressed in Vault 1.4.1 by configuring the
|
|
|
|
|
required metadata explicitly:
|
2020-05-13 23:55:32 +00:00
|
|
|
|
|
|
|
|
```
|
|
|
|
|
vault write auth/aws/config/identity \
|
|
|
|
|
ec2_metadata=account_id,auth_type,instance_id,region \
|
|
|
|
|
iam_metadata=account_id,auth_type,client_user_id,canonical_arn,inferred_entity_id,inferred_aws_region
|
|
|
|
|
```
|
2020-05-27 16:29:30 +00:00
|
|
|
|
2020-12-17 21:53:33 +00:00
|
|
|
@include 'ldap-upndomain-issue.mdx'
|
