By: Levente Kintzel user 09 Feb 2021 at 2:46 a.m. CST

4 Responses
Levente Kintzel gravatar
Hi, I would like to customize the error logo on Shibboleth IDP. I saw that the standard logo URL has been changed to `/servlet/logo`. I was digging a bit the source code, and realized that there is a servlet developed for that reason. https://github.com/GluuFederation/oxShibboleth/blob/master/oxLogoServlet/src/main/java/org/oxLogoServlet/IdpLogoServlet.java According to this it seems to me, that for custom logo we always receive the response false (because organization==null on the call) and will fallback to the default logo that has to be in the classpath next to the servlet. At the very end, I customized the `error.vm` and put back the original URL of the logo, but I'm sure that change from your side has been made on purpose and we cannot see why and our change can cause some regression problems. Can you advice pls? Thanks. Regards, Levente

By Michael Schwartz Account Admin 18 Feb 2021 at 6:03 p.m. CST

Michael Schwartz gravatar
@Dzouato Djeumen.Rolain Bonaventure any idea? If so, maybe we can add a note to the docs on how to do this for others?

By Mohib Zico Account Admin 28 Feb 2021 at 11:08 p.m. CST

Mohib Zico gravatar
Hi Levente, >> I would like to customize the error logo on Shibboleth IDP. Which logo? Can you please share screenshot?

By Levente Kintzel user 08 Mar 2021 at 3:15 a.m. CST

Levente Kintzel gravatar
Hi, So, the error screenshot looks like the attached one. It appears when I have an error during the SAML communication (ex: wrong metadata, missing configurations). It is raised by `Shibboleth`. In my `message.properties` I have the corresponding setup part: ``` idp.logo = /images/dummylogo.png idp.logo.alt-text = My Company LTD. idp.logo.target.url = http://www.mycompanyltd.com ``` Many thanks, Levente

By Karl Volz named 15 Apr 2021 at 12:56 p.m. CDT

Karl Volz gravatar
Hello Zico - My messages.properties is like Levente's. I would like to get an organization logo on the shib error pages here as well. Has this been addressed by web guys? (We are hoping to move 4.2.3 server to production soon. Everything else is looking good.) thanks, Karl