There is an environment variable in the guacamole docker image that could set
up the remote ip valve in tomcat, just add REMOTE_IP_VALVE_ENABLED: true and it
will do the job.
For mod_proxy, I believe that’s an issue for apache, if you are using nginx you
can ignore it.
Hi!
I have successfully set up Guacamole using docker by following the
Guacamole manual v1.5.5. Now I am setting up reverse proxy (NGINX docker)
for Guacamole. I have done the setting in NGINX and I am able to login
Guacamole through NGINX. But According to Guacamole manual, I need to do
the follo
On Thu, Feb 10, 2022 at 11:14 AM Martin Twerski
mailto:mar...@tigunia.com>> wrote:
Upgraded from 1.3 to 1.4 where I had SAML working. I have updated the plugin to
the new sso one. I get an error when trying to use SAML auth -
[http-nio-8080-exec-2] WARN o.a.g.a.s.a.AssertionConsumerServiceRes
On Thu, Feb 10, 2022 at 11:14 AM Martin Twerski wrote:
> Upgraded from 1.3 to 1.4 where I had SAML working. I have updated the
> plugin to the new sso one. I get an error when trying to use SAML auth -
> [http-nio-8080-exec-2] WARN o.a.g.a.s.a.AssertionConsumerServiceResource -
> Authentication
On Thu, Feb 10, 2022, 10:37 Martin Twerski wrote:
> Upgraded from 1.3 to 1.4 where I had SAML working. I have updated the
> plugin to the new sso one. I get an error when trying to use SAML auth -
> [http-nio-8080-exec-2] WARN o.a.g.a.s.a.AssertionConsumerServiceResource -
> Authentication atte
Upgraded from 1.3 to 1.4 where I had SAML working. I have updated the plugin to
the new sso one. I get an error when trying to use SAML auth -
[http-nio-8080-exec-2] WARN o.a.g.a.s.a.AssertionConsumerServiceResource -
Authentication attempted with an invalid SAML response: SAML response did n
