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
Fix Released
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: l3-ipam-dhcp
tags: added: l3-ipam-dhcp
Changed in neutron:
importance: Undecided → Medium
assignee: nobody → Miguel Lavalle (minsel)
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to neutron (master)

Fix proposed to branch: master

Changed in neutron:
assignee: Miguel Lavalle (minsel) → György Szombathelyi (gyurco)
status: New → In Progress
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to neutron (master)

Submitter: Jenkins
Branch: master

commit 91d048dbde83a52f43aceebaf1b1e1ef0937602d
Author: Gyorgy Szombathelyi <email address hidden>
Date: Wed Nov 16 14:37:38 2016 +0100

    Allow keystone v3 in the designate driver

    Using the loader from keystoneauth1, it is possible to easily use
    keystone v3 options in [designate].
    For the end user, it means she/he must specify designate.auth_type,
    then she/he can specify an Keystone v3 endpoint in designate.auth_url.

    Change-Id: I8bb02f11e60767dacdf6ac852979cfa82de1e08b
    Closes-bug: #1585976

Changed in neutron:
status: In Progress → Fix Released
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix included in openstack/neutron

This issue was fixed in the openstack/neutron development milestone.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers