Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1240878

Summary: websso does not prepend WEBROOT to redirect URL
Product: Red Hat OpenStack Reporter: Jamie Lennox <jlennox>
Component: python-django-openstack-authAssignee: Matthias Runge <mrunge>
Status: CLOSED ERRATA QA Contact: Mike Abrams <mabrams>
Severity: high Docs Contact:
Priority: high    
Version: 7.0 (Kilo)CC: jlennox, nkinder, yeylon
Target Milestone: z2Keywords: Triaged, ZStream
Target Release: 7.0 (Kilo)   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: python-django-openstack-auth-1.2.0-5.el7ost Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-10-08 12:22:35 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Jamie Lennox 2015-07-08 01:59:03 UTC 
Set up WebSSO, but on a system using WEBROOT and the Horizon site was running under /dashboard. Websso works correctly up until the Keystone Javascript tries to post the token back to Horizon, and gets a 404.

It is posting to hostname/auth/websso, not to hostname/dashboard/auth/websso

One fix is to use WEBROOT when generating the redirect URL.


We need to get this fixed in the kilo release as it's holding back websso deployments that use the /dashboard/ prefix which is at least packstack.
Comment 3 Jamie Lennox 2015-07-08 02:02:25 UTC 
To clarify this was already fixed and released upstream. We either need to backport the patch or rebase the package.
Comment 7 Matthias Runge 2015-07-10 19:13:42 UTC 
Missing commit:

https://git.openstack.org/cgit/openstack/django_openstack_auth/commit/?id=85b2aaea489f2e89e36bc08b99216939d8076462
Comment 10 Matthias Runge 2015-07-10 19:17:34 UTC 
Stable backport:
https://review.openstack.org/200686
Comment 20 errata-xmlrpc 2015-10-08 12:22:35 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2015:1874