Thanks, Nick. That worked just fine, although my redirect was sending me to the SAML authentication page. I changed EXTENSION_PRIORITY from "*,saml" to "saml", and users get sent right on to our IDP for authentication.
Rob Robert Spellman *Associate Director for Network Services* Information and Library Services Bates College p: 207-786-6422 a: 110 Russell Street, Lewiston, ME 04240 w: www.bates.edu e: [email protected] On Thu, Sep 18, 2025 at 9:37 AM Nick Couchman <[email protected]> wrote: > On Wed, Sep 17, 2025 at 10:38 AM Robert Spellman <[email protected]> > wrote: > >> I'm in the process of upgrading to 1.6.0, which we are running in >> kubernetes. I'm trying to redirect traffic sent to the base url to >> /guacamole. In version 1.5.x, we used to be able to put a redirect in >> /home/guacamole/tomcat/webapps/ROOT. >> >> So far, I've tried using a configmap that contains the contents of an >> index.html that performs the redirect, but the place I've identified that >> it does the most good is within the catalina-base directory created in >> /tmp, but the directory is created with mktmp, so the directory name is >> always changing when the container restarts. >> >> > Hi, Robert, > > You should be able, in your Kubernetes configuration, to specify the > WEBAPP_CONTEXT environment variable for the guacamole container, and set > the value of that to "ROOT", which will deploy Guacamole at the root (/) > context. Then, when you do your ingress configuration and/or route, just > point it to the root URL instead of Guacamole. Should not be any need to do > any redirection or anything like that. > > See: > https://guacamole.apache.org/doc/gug/guacamole-docker.html#the-guacamole-docker-image > > -Nick >
