secret_ref shouldn't be a barbican url

Bug #1730538 reported by Matthew Edmonds
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Barbican
Won't Fix
Undecided
Unassigned

Bug Description

secret_ref is an entire URL when it should only need to be an ID. The rest of the URL should be generated by the client based on the keystone service catalog or whatever it is using to know how to talk to Barbican.

E.g. 77bed80e-3632-4032-8435-d7eb753dff9a instead of https://127.0.0.1:9311/v1/secrets/77bed80e-3632-4032-8435-d7eb753dff9a

Revision history for this message
Matthew Edmonds (edmondsw) wrote :

You might be able to talk to barbican with several different URLs, e.g. 127.0.0.1, localhost, <hostname>, etc. so including one of those in the secret_ref is not only unnecessary but it probably also programmatic unless you are dynamically changing the secret_ref based on how the client addressed Barbican... which would have other issues... so just avoid all that and trim down to using only the ID.

Revision history for this message
Matthew Edmonds (edmondsw) wrote :

s/programmatic/problematic/

Revision history for this message
Grzegorz Grasza (xek) wrote :

Closing out bugs created before migration to StoryBoard. Please re-open if you are of the opinion it is still current.

Changed in barbican:
status: New → Incomplete
status: Incomplete → Won't Fix
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.