Accessing MiCollab Portal via External DNS 1

[kwbMitel]

Does anyone know if it is possible for the external default page to be the user portal in the same way that the internal default page is the user portal.

Security risk blah blah blah

Customer doesn't want to type 7 more characters.

 

[jpruder]

Are you using webproxy? Yes this can be done, the only thing that might break is remote system admin via proxy. I don't ever use that. I have changed the default not found to be instead

https://fqdn.com/portal.

I'll look at what template I adjusted and what line was changed and update when I can

 

[kwbMitel]

Yes, using web proxy, thanks

 

[jpruder]

This method will survive an upgrade. the concept to to change the default template file that creates the web httpd.conf file to a custom version of the same file.

This method also quick reversion back to the original setting.

1 First you make the directory structure for the custom location
mkdir -p /etc/e-smith/templates-custom/etc/httpd/conf/httpd.conf

2 Second copy the original file to be modified
cp /etc/e-smith/templates/etc/httpd/conf/httpd.conf/82WebProxyVirtualHosts /etc/e-smith/templates-custom/etc/httpd/conf/httpd.conf

3 Third is to edit this file
nano /etc/e-smith/templates-custom/etc/httpd/conf/httpd.conf/82WebProxyVirtualHosts

4, Fourth is to expand the templates that create the http.conf. The system will use any matching name from the custom-template directory
expand-template /etc/httpd/conf/httpd.conf

5. Lately your restart the httpd service
sv t /service/httpd-e-smith

I think it is line 89 that is modified from the original. Below is a copy of 82WebProxyVirtualHosts that has been modified

[link

https://files.engineering.com/getfi...bdb9-0e6cd5df3756&file=82WebProxyVirtualHosts

]Link[/url]

 

[kwbMitel]

That is an extremely detailed answer. Star awarded.

That is also far more than I am comfortable with changing to save a customer typing the word portal.

I would also surmise that this would not survive a redeployment or upgrade of a virtual server.

I'm impressed by your answer but I don't think it's for me.

 

[jpruder]

It should survive a restore from running server. MSL is a templated system. it uses fragments to create files. Most of these are stored in /etc/e-smith you will see default as well as custom. The nice thing about this is a temple in custom overrides the same name in default. The expand-template command basically rebuild the file using parts from both if there is a custom value, otherwise it is all from default. This way if your custom is wrong, you can delete it and issue the expand command and you are back at default.

Since this is part of the webpage configuration file, i.e this is part of the fragments that creates the httpd.conf file. The attachment files is fairly recent and I don't think much has changed with this since the addition of Lets Encrypt. You could likely create the custome template location structure and add this there. Do the expand and restart httpd-e-smith