Vault get_csr function is missing options (L locality, CN common_name)
Bug #1882599 reported by
Camille Rodriguez
This bug affects 2 people
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| vault-charm |
Fix Released
|
Undecided
|
Unassigned | ||
Bug Description
The vault charm limits the number of parameters that can be set when requesting a CSR. The code allows for : ttl, C (country), ST (province), OU (organizational unit), O (organization), see https:/
Currently, to be able to pass a L parameter, for example, one needs to use directly the vault API instead of the juju actions.
| tags: | added: cpe-onsite |
| summary: |
- Vault get_csr function is missing options (L locality, ST province) + Vault get_csr function is missing options (L locality, and others) |
| description: | updated |
Revision history for this message
| Jeff Hillman (jhillman) wrote Re: Vault get_csr function is missing options (L locality, and others) | #1 |
| summary: |
- Vault get_csr function is missing options (L locality, and others) + Vault get_csr function is missing options (L locality, CN commaon_lame) |
| summary: |
- Vault get_csr function is missing options (L locality, CN commaon_lame) + Vault get_csr function is missing options (L locality, CN commaon_name) |
| summary: |
- Vault get_csr function is missing options (L locality, CN commaon_name) + Vault get_csr function is missing options (L locality, CN common_name) |
Revision history for this message
| Jeff Hillman (jhillman) wrote | #2 |
| Changed in vault-charm: | |
| status: | New → Fix Committed |
| Changed in vault-charm: | |
| milestone: | none → 20.08 |
| Changed in vault-charm: | |
| status: | Fix Committed → Fix Released |
To post a comment you must log in.
It is almost missing the CN parameter to be changed. There is a customer requesting a particular CN for their CSR's due high audit compliancy.