Hello everyone,
we are currently looking for a persistent and preferably officially supported way to customize the IFS Cloud login / landing page background image.
We are running IFS Cloud 25.2.7.
Since IFS Cloud 25.2.2, we identified the login background image inside the ifsapp-proxy container at:
/usr/share/nginx/html/landing-page/background/IFS-CLOUD-SERV-INDUSTRIES.webp
Technically, we are able to replace the image by creating a Kubernetes Secret containing our custom background image and making it available to the ifsapp-proxy deployment.
This works, but our concern is that this is not an officially supported or upgrade-safe customization.
The customization could potentially be overwritten or lost during operations such as:
- Middle Tier restart / recreation
- Pod or deployment recreation
- IFS Installer execution
- Helm upgrade
- IFS Cloud update
- Redeployment of
ifsapp-proxy
We therefore contacted IFS Support to ask whether there is an officially supported way to configure the login background globally.
According to IFS Support, there is currently no officially supported method for customizing the IFS Cloud login background image. They also confirmed that the Appearance Designer does not currently provide this functionality and recommended raising the question within the IFS Community.
Browser extensions such as the "IFS Login Background Changer" were mentioned as a possible workaround, but this is not suitable for our use case because every individual user would have to install the extension locally.
Our goal is to have one centrally configured corporate background image that remains persistent across deployments and updates without requiring manual intervention.
Has anyone implemented something similar in IFS Cloud?
In particular, we would be interested to know:
- Is there a Helm value or Installer configuration that can be used to persistently override the landing page background?
- Is there a recommended way to mount a custom image into
ifsapp-proxywithout modifying the standard deployment directly? - Has anyone implemented this using a Kubernetes Secret, ConfigMap, additional volume mount or another mechanism that survives IFS Installer executions and upgrades?
- How do you prevent the customization from being overwritten when IFS recreates the
ifsapp-proxydeployment? - Are there any known plans for IFS to provide login page branding through the Appearance Designer or another standard configuration?
We are not looking for a browser-side/user-specific solution. The requirement is a central, environment-wide and upgrade-safe configuration.
Any experience or recommendations would be greatly appreciated.
Best regards
Erik