Endpoint argument is ignored if authentication is used
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
python-barbicanclient |
Fix Released
|
High
|
Douglas Mendizábal |
Bug Description
When you provide both auth and endpoint arguments, the endpoint is completely ignored.
Example:
barbican --os-username {username} --os-password {password} --os-tenant-name {tenant} --os-auth-url {auth_uri} --endpoint {endpoint_uri} secret store --name 'test'
The client uses the uri provided in the service catalog on auth and completely ignore the endpoint given explicitly as an argument. This shouldn't be the case. If the user explicitly specifies a different endpoint, then that is what should be used. This especially affects test environments where you will be targeting a development endpoint that is different than what is listed in the keystone service catalog.
Tests:
- All CLI tests when auth is configured.
Changed in python-barbicanclient: | |
assignee: | nobody → Douglas Mendizábal (dougmendizabal) |
milestone: | none → 3.0.0 |
Changed in python-barbicanclient: | |
status: | Fix Committed → Fix Released |
This doesn't seem to be a bug? If you authenticate against a keystone instance, the only services that should accept that token have to be in that keystone's service catalog. Why would you need to authenticate against a keystone and use a service not in its catalog?