Hide Forgot
Description of problem: We support accessing engine via reverse proxy under different name, so it is accessible both from LAN via its real FQDN and from other networks via different FQDN. See https://bugzilla.redhat.com/show_bug.cgi?id=1353093#c8 This should also work for SSO, I made it work as written here: https://bugzilla.redhat.com/show_bug.cgi?id=1353093#c9 This BZ is for consideration to document it and/or support this setup. Version-Release number of selected component (if applicable): 4.x How reproducible: 100% Steps to Reproduce: 1. do SSO access rhvm which is configured to be accessed via reverse proxy 2. 3. Actual results: it works but let's consider if this setup is right and we do document or support it Expected results: it should be clear if we have documentation and/or support for this setup Additional info:
Plus, opening consoles should work of course.
Engine part of configuration which is needed for accessing via reverse proxy is described in Doc Text of BZ1325746 and BZ1362196, the only piece missing is the configuration of that reverse proxy (but that's probably out of RHV doc scope). If we want to support reverse proxy as one of allowed RHV setups, then we should add those configurations to official RHV documentation. So moving bug to documentation team.
This bug was opened back in 2016--four years ago. It has not been addressed yet, and there are many other issues with higher priority. If this was a quick fix I would address it, but based on the info in the bug, it appears to be an investment in resource time that is not worth the ROI. So I am closing this as WILLNOTFIX. If you disagree with this resolution, please reopen the bug and assign it the correct priority.