By: Colt McCormack user 08 Jul 2020 at 5:03 p.m. CDT

2 Responses
Colt McCormack gravatar
I'm having an issue customizing the 4.1 public pages. I have successfully customized these pages before in 3.1.2. I am able to successfully change pages themselves in 4.1, but cannot reference static resources. I am following the [4.1 documentation for customizing public pages](https://gluu.org/docs/gluu-server/4.1/operation/custom-design/). I have created a stylesheet folder, placed a file in it with a few lines of test CSS, and chowned it to the jetty user/group. ``` mkdir -p /opt/gluu/jetty/oxauth/custom/static/stylesheet/ nano /opt/gluu/jetty/oxauth/custom/static/stylesheet/style.css chown -R jetty:jetty /opt/gluu/jetty/oxauth/custom/static/ ``` I restarted oxauth (as well as the entire container in later attempts) and navigate to : https://mydomain.com/oxauth/ext/resources/stylesheet/style.css and receive the generic Gluu 404 error page. Same result for the logo I placed at /opt/gluu/jetty/oxauth/custom/static/img/logo.png. These 404s are also there when trying to use it in a page, for example: ``` nano /opt/gluu/jetty/oxauth/custom/pages/WEB-INF/incl/layout/login-template.xhtml ``` ```html <link type="text/css" rel="stylesheet" href="/oxauth/ext/resources/stylesheet/style.css" /> ``` Result persists with different browsers, incognito windows, and browser cache refresh. Is it possible that something changed in 4.0 or 4.1 and the docs weren't updated from 3.1.x?

By Colt McCormack user 10 Jul 2020 at 1:48 p.m. CDT

Colt McCormack gravatar
After diffing my upgraded server against a fresh 4.1 install I can confirm that the `/opt/gluu/jetty/oxauth/webapps` folder is missing ``` oxauth.xml oxauth_web_resources.xml ``` and the `/opt/gluu/jetty/identity/webapps` folder is missing ``` identity.xml identity_web_resources.xml ``` I can confirm that copying these files manually fixes the issue and customizations can proceed as per the documentation. This happens on a fresh 3.1.2 server (to match our production server version) which has data imported and is then upgraded to 4.0 and then 4.1 using the upgrade documentation for each version. I believe this is a bug in the 4.0 upgrade script. What would be the appropriate repo to file an issue in?

By Mohib Zico Account Admin 14 Jul 2020 at 1:51 p.m. CDT

Mohib Zico gravatar
Hi Colt, >> I believe this is a bug in the 4.0 upgrade script. Thanks much for your report. We will test it as soon as we can manage some time. Thanks again!