secret_ref shouldn't be a barbican url
Bug #1730538 reported by
Matthew Edmonds
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-
To post a comment you must log in.
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.