I really do not understand where your portal.json file comes from. Normally portal.json should not exist in the file system; instead, it’s generated on the fly by the daemon univention-portal-server. Here’s the relevant portion of the Apache configuration file /etc/apache2/ucs-sites.conf.d/univention-portal.conf:
ProxyPass /univention/portal/portal.json http://127.0.0.1:8095/ retry=0
ProxyPassReverse /univention/portal/portal.json http://127.0.0.1:8095/
However, as soon as a file with the same name exists in /var/www/univention/portal, that file takes precedence over those proxy rules (not sure why).
On none of my systems does /var/www/univention/portal/portal.json exist.
Therefore I suggest you delete that file, clear your browser cache and try again.
Well, before you do that, you should use curl for verifying that removing the file changes the situation. Before you remove it, run the following:
curl https://$(hostname -f)/univention/portal/portal.json > portal-before.json
rm /var/www/univention/portal/portal.json
curl https://$(hostname -f)/univention/portal/portal.json > portal-after.json
Then compare the two files. They shouldn’t match; in fact, the portal-after.json should probably contain the correct portal layout as configured in LDAP.
m.