<div dir="ltr"><div>On 24 January 2017 at 15:15, <a href="mailto:emanuel.santosvarina@mahle.com">emanuel.santosvarina@mahle.com</a> wrote: <br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><font face="sans-serif" size="2">If I access the UI via "ALIAS"
I get the Error-Page "The client is not authorized to request an authorization.
It's required to access the system using FQDN.</font>
<br>
<br><font face="sans-serif" size="2">What can I do to get UI working through
ALIAS and real hostname?</font>
<br></blockquote><div><br>The Hosted-Engine should be installed &
configured with the correct FQDN to begin with. Changing it post install
is currently unsupported & can cause a whole host of problems.
There are a couple of documented cases where people have attempted to do
so with varying success, but non have come out problem free.<br></div><div><br>I'm
currently in the same situation after a company domain change and have
decided that the risk of unforeseen issues & potential problems down
the line, are far greater than the pain of redeploying & migrating
to a new environment.<br></div><div><br></div>A really hacky hack,
without interfering with the engine, would be to try & put a reverse
proxy in front, but that'll require a load of dynamic rewriting filters
to work.<div class="gmail_extra"><br><br><div class="gmail_quote">On 24 January 2017 at 11:41, Juan Hernández <span dir="ltr"><<a href="mailto:jhernand@redhat.com" target="_blank">jhernand@redhat.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div class="gmail-HOEnZb"><div class="gmail-h5">
</div></div>Create a 99-whatever-you-like.conf file in<br>
/etc/ovirt-engine/engine.conf.<wbr>d with the following content:<br>
<br>
SSO_ALTERNATE_ENGINE_FQDNS="<wbr>thealias"<br>
<br>
Then restart the engine:<br>
<br>
systemctl restart ovirt-engine<br>
<br>
This setting is documented here:<br>
<br>
<br>
<a href="https://github.com/oVirt/ovirt-engine/blob/master/packaging/services/ovirt-engine/ovirt-engine.conf.in#L363-L366" rel="noreferrer" target="_blank">https://github.com/oVirt/<wbr>ovirt-engine/blob/master/<wbr>packaging/services/ovirt-<wbr>engine/ovirt-engine.conf.in#<wbr>L363-L366</a><br></blockquote><div><br></div><div>AFAIK, the SSL certificates will still need updating & I've read of people still having other issues due to differing FQDNs. Being able to update the HE's FQDN would be of big interest to me, but I've not yet seen one case where it didn't end with anomalies...<br></div></div><br clear="all"><br>-- <br><div class="gmail_signature">Doug</div>
</div></div>