Barbican certificate import issue

Bug #2034990 reported by Satish Patel
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
skyline apiserver
Fix Released
Undecided
Unassigned

Bug Description

I have deployed latest skyline with Zed openstack release. I am playing with octavia and Barbican secret store. When I am trying to import my SSL certificate I am getting strange private key validation issue. Same key works when I use command line to import certificate in barbican.

Please enter a correct private key, format is refer to the left tip!

I have tried multiple keys but everyone throwing same errors but nothing works here.

Revision history for this message
Satish Patel (satish-txt) wrote :

Find attached screenshot

Revision history for this message
Satish Patel (satish-txt) wrote :

Any update?

Changed in skyline-apiserver:
assignee: nobody → conna (yangshaoxue)
Revision history for this message
xusongfu (xusongfu) wrote :

Hi,

I cannot determine the cause of this problem, because the image you provided cannot see the complete characters.

The images of correctly formatted characters can be referenced in the attachment.

If you have any other questions, welcome your feedback.

Thank you.

Revision history for this message
xusongfu (xusongfu) wrote :
Revision history for this message
xusongfu (xusongfu) wrote :
Changed in skyline-apiserver:
status: New → Incomplete
Revision history for this message
Satish Patel (satish-txt) wrote :

Give me few minutes and I will upload new screenshot. Still I am uploading my cert and key file here so its not something copy paste issue.

Why skyline saying or throwing error that its invalidate?

Revision history for this message
conna (yangshaoxue) wrote :
Revision history for this message
conna (yangshaoxue) wrote :

The certificate requires RSA encryption.

Skyline verifies '-----BEGIN RSA PRIVATE KEY-----' and '-----END RSA PRIVATE KEY-----'.

Revision history for this message
Satish Patel (satish-txt) wrote :

Oh wait, so "RSA" keyword has to be there?

Damn when I generate certificate on my compute it just generated crt and key file without RSA keyword. So I was just uploading that as it as.

Why do we have hard requirement to have "RSA" keyword in key?

Revision history for this message
conna (yangshaoxue) wrote :

Barbican in Skyline is only used to store certificates for Octavia.

For safety and effectiveness, we strictly restrict certificates to RSA format.

In the future, Skyline will consider relaxing the restrictions to support more certificate formats.

Revision history for this message
Satish Patel (satish-txt) wrote :

Shouldn’t be put warning or error related RSA instead just saying invalid? I burn my brain behind this and found it required RSA. What if I just change keyword to RSA and keep cipher different? How does it validate that it’s true RSA?

conna (yangshaoxue)
Changed in skyline-apiserver:
assignee: conna (yangshaoxue) → nobody
assignee: nobody → conna (yangshaoxue)
assignee: conna (yangshaoxue) → nobody
xusongfu (xusongfu)
Changed in skyline-apiserver:
status: Incomplete → In Progress
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix included in openstack/skyline-console 3.0.0.0rc2

This issue was fixed in the openstack/skyline-console 3.0.0.0rc2 release candidate.

Revision history for this message
Satish Patel (satish-txt) wrote :

Just curious that what is the fix here? I didn’t see patch anywhere.

Revision history for this message
xusongfu (xusongfu) wrote (last edit ):
Changed in skyline-apiserver:
status: In Progress → Fix Committed
status: Fix Committed → Fix Released
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix included in openstack/skyline-console 4.0.0.0rc1

This issue was fixed in the openstack/skyline-console 4.0.0.0rc1 release candidate.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.