Designate plugin lacks of Keystone authentication options
Bug #1585976 reported by
György Szombathelyi
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
neutron |
Fix Released
|
Medium
|
György Szombathelyi |
Bug Description
The designate plugin has a very simple keystone authentication:
- It supports only keystone v2
- It doesn't honor any certificates (client or CA), nor insecure TLS option
It would be good to re-use the nova auth part (even the keystoneauth1 lib).
tags: | added: l3-ipam-dhcp |
Changed in neutron: | |
importance: | Undecided → Medium |
assignee: | nobody → Miguel Lavalle (minsel) |
To post a comment you must log in.
Fix proposed to branch: master /review. openstack. org/398359
Review: https:/