Solve token expiration issue
Bug #1506670 reported by
hongbin
This bug affects 2 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Magnum |
Fix Released
|
Medium
|
Hua Wang |
Bug Description
This bug is for tracking Wanghua's comment in the following review:
https:/
In particular, here is the comment:
I think we shouldn't use user_token in swarmnode to communicate with magnum for TLS certs. Token has expiration time.
In summary, magnum passes user token to bays. The token is used by the bay nodes to communicate with Magnum and/or other OpenStack service. The token is created at "magnum bay-create ..." and it might expire at "magnum bay-update ..."
Changed in magnum: | |
milestone: | none → mitaka-1 |
Changed in magnum: | |
status: | New → Triaged |
importance: | Undecided → Medium |
Changed in magnum: | |
assignee: | nobody → Hua Wang (humble00) |
Changed in magnum: | |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
This bug is addressed by https:/ /blueprints. launchpad. net/magnum/ +spec/create- trustee- user-for- each-bay