Magnum

Introduce keystone trust for k8s bay

Bug #1504350 reported by yuanying
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Magnum
Fix Released
Critical
yuanying
Magnum mitaka-1

Bug Description

Hongbin said below

> Thanks for the great work. One thing I just discovered is that this patch directly passes user's token to heat, which is exposed within the tenant. I have concerns of exposing a unscoped token here. I wish you have a following up patch to switch to keystone trust.

* https://review.openstack.org/#/c/202873/

yuanying (yuanying)
Changed in magnum:
assignee: nobody → yuanying (ootsuka)
Revision history for this message
hongbin (hongbin034) wrote :

@yuanying, just let you know that there is a patch proposed to swarm bay. You might interest to take a look.

https://review.openstack.org/#/c/232152/

hongbin (hongbin034)
Changed in magnum:
importance: Undecided → Critical
Adrian Otto (aotto)
Changed in magnum:
milestone: none → mitaka-1
Revision history for this message
Hua Wang (humble00) wrote :

This bug is addressed by https://blueprints.launchpad.net/magnum/+spec/create-trustee-user-for-each-bay.

Changed in magnum:
status: New → Fix Committed
Revision history for this message
Spyros Trigazis (strigazi) wrote :

I believe this is fixed by https://review.openstack.org/#/c/296926/

Changed in magnum:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

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