Bug 1362196 – aaa: Add support for dynamic porting

Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.

Bug 1362196 - aaa: Add support for dynamic porting

Summary:	aaa: Add support for dynamic porting

Status:	CLOSED CURRENTRELEASE

Aliases:	None

Product:	ovirt-engine
Classification:	oVirt
Component:	AAA (Show other bugs)
Sub Component:
Version:	4.0.0
Hardware:	Unspecified Unspecified

Priority	unspecified Severity medium (vote)
Target Milestone:	ovirt-4.0.4
Target Release:	4.0.4
Assigned To:	Ravi Nori
QA Contact:	Aleksei Slaikovskii
Docs Contact:

URL:
Whiteboard:
Keywords:

Depends On:
Blocks:	1353093 1376330
	Show dependency tree / graph

Reported:	2016-08-01 09:41 EDT by Ravi Nori
Modified:	2016-11-11 00:10 EST (History)
CC List:	8 users (show)

See Also:
Fixed In Version:
Doc Type:	Enhancement
Doc Text:	A new configuration variable called ENGINE_SSO_INSTALLED_ON_ENGINE_HOST has been added. This flag can be used to specify if the SSO service is installed on the same host as the engine or installed on a different host. If this flag is set to true, the URL and port used to access the Manager is used to redirect to the login page. If this flag is set to false, the value set in ENGINE_SSO_AUTH_URL is used to redirect user to the login page.
Story Points:	---
Clone Of:
Clones:	1376330 (view as bug list)
Environment:
Last Closed:	2016-09-26 08:31:05 EDT
Type:	Bug
Regression:	---
Mount Type:	---
Documentation:	---
CRM:
Verified Versions:
Category:	---
oVirt Team:	Infra
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---

Flags:	rule-engine: ovirt‑4.0.z+ mgoldboi: planning_ack+ mperina: devel_ack+ pstehlik: testing_ack+

Attachments	(Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

External Trackers
Tracker	ID	Priority	Status	Summary	Last Updated
oVirt gerrit	61249	master	MERGED	aaa: Add support for dynamic porting	2016-08-02 06:27 EDT
oVirt gerrit	61846	ovirt-engine-4.0	MERGED	aaa: Add support for dynamic porting	2016-08-03 03:42 EDT

Groups: None (edit)

Description Ravi Nori 2016-08-01 09:41:00 EDT

Description of problem: When the manager is behind a NAT network (with port-forwarding to the correct https port) the landing page tries to redirect the browser back to port 80, resulting in failure to see login page.

Version-Release number of selected component (if applicable): 4.0


How reproducible: 


Steps to Reproduce:
1. Setup port forwarding
2. Access engine using alternate port

Actual results: Engine redirects request to port 80.


Expected results: Engine uses port number from request.

Comment 1 Martin Perina 2016-08-02 06:28:17 EDT

Moving back to POST, we need backport to ovirt-engine-4.0 branch

Comment 3 Aleksei Slaikovskii 2016-09-13 09:16:11 EDT

Verified rhevm-4.0.4.1-0.1.el7ev.noarch

Note You need to log in before you can comment on or make changes to this bug.