Add public_endpoint option like other service

Bug #1493873 reported by Kevin Tibi
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
OpenStack Heat
Triaged
Medium
Unassigned

Bug Description

Many openstack service (like keystone) use public_endpoint option for force the URL return by service when you use proxy.

In my case :

USER ==> PROXY HTTPS(proxy) ===> PROXY LOCAL HTTPS (control)=====>HEAT API HTTP control)

On control ==> RequestHeader set X-Forwarded-Proto "https"

heat.conf ==> secure_proxy_ssl_header = X-Forwarded-Proto

[root@control ~(keystone_admin)]# curl https://control:8004/
{"versions": [{"status": "CURRENT", "id": "v1.0", "links": [{"href": "https://control:8004/v1/", "rel": "self"}]}]}

[root@proxy ~(keystone_admin)]# curl https://proxy/orchestration/
{"versions": [{"status": "CURRENT", "id": "v1.0", "links": [{"href": "https://proxy/v1/", "rel": "self"}]}]} <======== NEED TO RETURN href": "https://proxy/orchestration/v1/"

Kevin Tibi (ktibi)
description: updated
Revision history for this message
Adrien Cunin (adri2000) wrote :

Confirmed, experienced exact same issue...

See also bug #1444490.

Changed in heat:
status: New → Confirmed
Changed in heat:
milestone: none → mitaka-1
importance: Undecided → Medium
status: Confirmed → Triaged
Changed in heat:
milestone: mitaka-1 → mitaka-2
Changed in heat:
milestone: mitaka-2 → mitaka-3
Changed in heat:
milestone: mitaka-3 → mitaka-rc1
Changed in heat:
milestone: mitaka-rc1 → newton-1
Thomas Herve (therve)
Changed in heat:
milestone: newton-1 → next
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

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