1---
2layout: "docs"
3page_title: "Upgrading to Vault 0.9.1 - Guides"
4sidebar_title: "Upgrade to 0.9.1"
5sidebar_current: "docs-upgrading-to-0.9.1"
6description: |-
7  This page contains the list of deprecations and important or breaking changes
8  for Vault 0.9.1. Please read it carefully.
9---
10
11# Overview
12
13This page contains the list of deprecations and important or breaking changes
14for Vault 0.9.1 compared to 0.9.0. Please read it carefully.
15
16### AppRole Case Sensitivity
17
18In prior versions of Vault, `list` operations against AppRole roles would
19require preserving case in the role name, even though most other operations
20within AppRole are case-insensitive with respect to the role name. This has
21been fixed; existing roles will behave as they have in the past, but new roles
22will act case-insensitively in these cases.
23
24### Token Auth Backend Roles Parameter Types
25
26For `allowed_policies` and `disallowed_policies` in role definitions in the
27token auth backend, input can now be a comma-separated string or an array of
28strings. Reading a role will now return arrays for these parameters.
29
30### Transit Key Exporting
31
32You can now mark a key in the `transit` backend as `exportable` at any time,
33rather than just at creation time; however, once this value is set, it still
34cannot be unset.
35
36### PKI Secret Backend Roles Parameter Types
37
38For `allowed_domains` and `key_usage` in role definitions in the PKI secret
39backend, input can now be a comma-separated string or an array of strings.
40Reading a role will now return arrays for these parameters.
41
42### SSH Dynamic Keys Method Defaults to 2048-bit Keys
43
44When using the dynamic key method in the SSH backend, the default is now to use
452048-bit keys if no specific key bit size is specified.
46
47### Consul Secret Backend Lease Handling
48
49The `consul` secret backend can now accept both strings and integer numbers of
50seconds for its lease value. The value returned on a role read will be an
51integer number of seconds instead of a human-friendly string.
52
53### Unprintable Characters Not Allowed in API Paths
54
55Unprintable characters are no longer allowed in names in the API (paths and
56path parameters), with an extra restriction on whitespace characters. Allowed
57characters are those that are considered printable by Unicode plus spaces.
58