Stored key certificate order does not set PK on generated container
Bug #1459454 reported by
John Wood
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Barbican |
Fix Released
|
High
|
Juan Antonio Osorio Robles | ||
Bug Description
When a certificate-type order is placed with the 'stored-key' request type, the generated certificate-type container does not have the 'private-key' secret reference filled out.
So the following sequence reveals the error:
1) Place an asymmetric-type order with Barbican, which should eventually produce an asymmetric-type container, with a 'private-key' secret reference to the stored encrypted private key.
2) Place a certificate-type order with Barbican, with the container-ref set to the asymmetric key from step (1).
3) View the certificate-type container generated from (2). It does not have the 'private-key' reference filled out, but should have the same one set in (1) above (hence this private-key secret will be in two containers at once).
Revision history for this message
| Juan Antonio Osorio Robles (juan-osorio-robles) wrote | #1 |
Revision history for this message
| John Wood (john-wood-w) wrote | #2 |
| Changed in barbican: | |
| assignee: | nobody → Juan Antonio Osorio Robles (juan-osorio-robles) |
| Changed in barbican: | |
| status: | New → In Progress |
Revision history for this message
| OpenStack Infra (hudson-openstack) wrote Fix merged to barbican (master) | #3 |
| Changed in barbican: | |
| status: | In Progress → Fix Committed |
| Changed in barbican: | |
| milestone: | none → liberty-2 |
| status: | Fix Committed → Fix Released |
| Changed in barbican: | |
| importance: | Undecided → High |
| Changed in barbican: | |
| milestone: | liberty-2 → 1.0.0 |
To post a comment you must log in.
Was this supposed to be the expected behaviour? Seems to me like none of the plugins take this into consideration. And even the ResultDTO that's gotten from the certificate order has no reference of a private key in it.