Univention Bugzilla – Bug 35456
ini should support WebInterfacePort
Last modified: 2015-03-11 15:10:03 CET
Some apps install web interfaces at some non-standard port. The App Center does not support this, so the ISVs are bound to do some workarounds to register these web interfaces in the ucs-overview.
Workarounds: Write a postinst/postrm to set UCR variables by hand or add a redirect in Apache.
It would be nice to have WebInterfacePort so that this is not needed anymore.
One may argue that the port must be something else than 80/443. Alternatively, one allows these ports and sets the protocol explicitly if these values are given.
It think it is good to add the possibility to define a port for the App's web interface.
The problem with ports is the Amazon EC2 environment or any other virtualization that blocks access to instances for non-whitelisted ports. Each Amazon instance is secured by a security group that e.g. allows ports 22, 80 and 443. In such an environment other ports will not work and therefore the app's web interface cannot be reached. It is not possible to add other ports to an existing security group. A new security group has to be defined and assigned to the instance when switched off.
A better approach would be to create a reverse proxy from <fqdn>/<app name> → localhost:port/.
Would it be possible to add a feature that automatically creates such a reverse proxy setting automatically by the App Center, as soon as such a port is defined? I rate this feature as quite usefull for the ISVs. But, does it work generically for all apps providing the web interface via an own port?
*** Bug 37348 has been marked as a duplicate of this bug. ***
again, Ticket #2014121521000054
Alex and me discussed that the directive WebInterface should support URL's like ":8090/myserver" instead of a new variable WebInterfacePort.
I am adjusting this in the appcenter and UCS-overview.
Created attachment 6664 [details]
Attached is a patch which would do this. As Dirk and I discussed it's better to also add WebInterfacePort in the ini file. The hunk for the ucs-overview can be taken from the patch. The appcenter hunk would have to be adapted.
Supporting needs changes in umc-appcenter and univention-apache. The latter package has another pending patch (Bug #37566) so we cannot release it now.
But as it is a new UCR variable, ucs-overview may just ignore it for the time being. umc-appcenter is patched and built.
With this patch, the Dev Guide and the App Tutorial need to be adjusted.
Setting to assigned as you committed already.
*** Bug 37944 has been marked as a duplicate of this bug. ***
(In reply to Florian Best from comment #9)
> *** Bug 37944 has been marked as a duplicate of this bug. ***
→ Bug was introduced here.
Can you also have a look at the URI of andiga groupware migration? If it is installed it has a link ("open") which has broken URlencoding in its URL ('&' instead of &)
(In reply to Florian Best from comment #11)
> Can you also have a look at the URI of andiga groupware migration? If it is
> installed it has a link ("open") which has broken URlencoding in its URL
> ('&' instead of &)
/ucs-overview fixed in
As discussed: We also need to specify the protocol scheme (http/https) belonging to that port.
What about web interfaces which support http on port 81 and https on port 444?
Added WebInterfacePortHTTP and WebInterfacePortHTTPS and ucs/web/.../port_http and .../port_https resp.
set_registry_var('ucs/web/overview/entries/service/webweaver/port_http', '81') ERROR 'int' object has no attribute 'decode'
" Uncaught SyntaxError: Unexpected token }" when opening the link to the UMC module
OK: all other appcenter functionality