That did the trick. Thank you!!(Sent from mobile) Jacob Chapman GUACAMOLE_HOME is env is missing in container as far as I see on your screenshot. It should be in new builds of client: But I am afraid it is not in 1.5.5 from dockerhub which you probably are using. Try to set GUACAMOLE_HOME=/etc/guacamole in container and put logback.xml there. Thanks Anakien. That’s extremely helpful. I now understand GuacD logging is completely separate from the guacamole container logs.
I tried adding the logback.xml file to the home directory using the example on Guacamole’s documentation. Unfortunately I don’t get additional messages in the logs.
<Screenshot 2025-02-01 at 5.14.51 PM.png>
Thx,
Hi, SAML auth which you are speaking about, most probably is this one: Which is an extension for apache guacamole frontend part, not for guacd, which is the backend part. GUACD_LOG_LEVEL=debug set debug logging for guacd, but you would never see anything about auth issues there since it doesn't make auth at all. Just translate remote protocol into ws known language for a web client.
In order to debug auth on frontend end, you have to use this one: You have to put logback.xml into GUACAMOLE_HOME dir (depends on your docker image, there is a chance you have to set it if it is not set by default) with logging config. Hi,
I am getting this error when Guacamole attempts to use SAML authentication:
‘Request could not be processed: Could not parse SAML IdP Metadata file’.
I have a different Guacamole instance connected to a different IdP, which is working great. There is something very nuanced causing the error, because the two IdP configurations and nearly identical.
Is there any way to get more info on what’s causing the parsing error? I’m running in docker and tried setting GUACD_LOG_LEVEL=debug, but there’s still no additional detail.
Thanks,
|
