Groupwise Webaccess branding fails when calling Webconfig

Groupwise 2023.4

Hello,

I've tried several ways and several servers to get our logo to be shown in Groupwise Webaccess.

If I try in browser, I can see the logo. Inserting a webaddress pointing to our logo in GW-admin using  "http://...ourLogo.jpg" fails with:

ERROR: Unable to download the custom login logo image.
Reason: (domainname).de
Resolve the above issue and run this tool again.
INFO: SMGList is empty.

or error 400, if the website doesnt accept http://

Do I use https:... instead it will lead to

ERROR: Unable to download the custom login logo image.
Reason: Unsupported or unrecognized SSL message
Resolve the above issue and run this tool again.
INFO: SMGList is empty.


We are using a proxy server without authentication for web access. The server has no problem to contakt external addresses.

Any idea to solve this problem?

Holger

  • 0  

    Is the image a suitable size?  The logo of yours I did find is larger than the Docs indicate.

    It might be worth forcing the logo to the sizes listed or direct multiples of the size listed as part of the test.

    Hopefully the webconfig tool doesn't have a limit on how many levels onto the site to trip over, such the 4 folder levels that I found your logo in. 

    and a note of Terminology Correction, the last version of WebAccess is 18.2,  this is clearly the GW Web client,  or GWWeb as we say as a shorthand.  
      When you say WebAccess,  we think you are dealing with the old and unsupported Tomcat based web interface.

    ________________________

    Andy of KonecnyConsulting.ca in Toronto
    Please use the "Like" and/or "Verified Answers" as appropriate as that helps us all.

  • 0  

    the error is http 400

    https://en.wikipedia.org/wiki/List_of_HTTP_status_codes

    look here for the 400 reason and consider whether the gwweb can access the url at all. Is it possible to copy the jpg local with wget on the system on which the docker container with gwweb is running?

    INFO: SMGList is empty. is a hint when gwweb is configured and the configuration of the SMG is missing beforehand, so it is about gwweb

    Andy gives the hint Size Image, please note

    “You can't teach a person anything, you can only help them to discover it within themselves.” Galileo Galilei

  • 0  

    I have some more questions, Holger.

    You have mentioned version GW23.4. But as far as I can remember the "logo feature" came in with version 24.1 ...

    (more questions will follow after your reply)


    Use "Verified Answers" if your problem/issue has been solved!

  • Suggested Answer

    0  

    Did you maybe pull the webconfig ( and web ) without a tag as this means you get the tag :latest and this means 24.3, so as Diethmar mentioned the customization is not in 23.4 and this could be the root of the issue.

    The 23.4 backend just has no clue what the 24.3 web-config is asking as the REST API does not yet have the URL(s) for the customization part, so http error 400 meaning "bad request" sounds about the right error

    Can you check if all workswhen you pull it with the tag for 23.4 as found here


    hub.docker.com/.../tags
    https://hub.docker.com/r/mfgroupwise/web/tags

    So for 23.4 you use

    docker pull mfgroupwise/web-config:23.4.0

    docker pull mfgroupwise/web:23.4.0

    After that use this to run the image using the same tag mfgroupwise/web-config:23.4.0 and mfgroupwise/web:23.4.0

  • 0 in reply to   

    Hello,


    I'm very sorry for doing the mistake swapping digits,
    we use GW 24.3

    Holger

  • 0   in reply to 

    Did you check the things Andy and/or Georg mentioned?


    Also can you in a browser see the image using the same URL as you use in gwadmin as this should work as well

  • 0   in reply to 

    ok, so I return with my next question: did you run the webconfig part after you have feed the gw admin? webconfig tries to download logo and background jpg into a directory.

    Your config directory should be similar to this:

    I assume that your jpg files will have different names. Wink


    Use "Verified Answers" if your problem/issue has been solved!

  • 0   in reply to   

    In addition to what Diethmar has correctly stated here, a small addition:

    in /opt/novell/gw/ there is the file customlogin.json and additionally there should be the jpg files of the branding. These are the same files that are in the Docker directory that Diethmar specified above.

    Before changing anything in the config of gwweb, make sure that the URLs that refer to the image files are available in GWadmin. It is absolutely necessary to use https as protocol, also the URL should not contain an IP but the FQDN of the web server and the files should be located on a web server in the same subnet on which the GWWeb service has been installed.

    Finally, one more thing from the field. When I run into a problem like this it has always proven to be a good solution to remove unnecessary Docker images and only use what is required. There have been cases in the field where “old” images have left behind “old” config files. A clean Docker container also helps in terms of security.

    George

    “You can't teach a person anything, you can only help them to discover it within themselves.” Galileo Galilei

  • 0 in reply to   

    The logo is 210x210 px.

    If I use the logo placed in a subdir of a local visible webserver webconfig will not show the http(s) errors, only "INFO: SMGList is empty.".

    Looking in opt/novell/gw/customlogin I'll find the image file, I entered in the field in gwadmin - this seems to work.

    But: When I call the gw login page the logo isn't shown. Checking the logo source (open grafic in new tab) the filename isn't the name of the image  file I entered; it is an old entry I deleted many tries before.It seems, web confing doessn't change the entries in the active container.

    Holger

  • Suggested Answer

    0 in reply to 

    Ok, sometimes browsers cache is the problem.

    The browser I used to control the results of my tryings showed allway the same page because it has cached the gw login site and didn't refresh it.

    Now I think I can work with the results for optimizing them.

    Thanks for your suggestions,

    Holger