The issue with that is Guacamole provides no method for
authenticating against NIS so that does me no good. I don't want to
change 20 machines over from NIS to LDAP just to get this to work. Many
of the clients are not terribly Linux savvy, adding an additional layer
is NOT beneficial
The headers that you've been working with here will only affect whether
Tomcat and Guacamole see you as coming from your actual IP address
instead of the address of the proxy in front of Tomcat.
The destination remote desktop will always see the connecting client
address as that of the
I apologize, someone replied to this and I accidentally deleted
your reply, but you asked what IP was tomcat logging, and if I'm looking
in the right place, in catalina.out:
catalina.out:[2023-08-04 17:35:02] [info] 17:35:02.572
[http-nio-8080-exec-8] INFO
If you use a connection, what IP address does Guacamole record in the
history as being your source address?
- Mike
On 8/4/23 23:59, Robert Dinse wrote:
nslookup localhost
Server: 127.0.0.53
Address: 127.0.0.53#53
Non-authoritative answer:
Name: localhost.eskimo.com
Address:
nslookup localhost
Server: 127.0.0.53
Address: 127.0.0.53#53
Non-authoritative answer:
Name: localhost.eskimo.com
Address: 127.0.0.1
root@inuvik:~# grep localhost /etc/hosts
127.0.0.1 localhost localhost.localdomain loghost
On 8/4/23 22:35, Michael Jumper wrote:
It's
It's possible that "localhost" on your system maps to the IPv6 address
for localhost, so the source address of your proxy doesn't actually
match the value you specified for "internalProxies".
- Mike
On 8/4/2023 6:12 PM, Robert Dinse wrote:
I still haven't gotten Apache external
I still haven't gotten Apache external authentication to work
properly. I did manage to get mod_authnz_external to peacefully
co-exist with mod_suphp, the secret was to compile mod_authnz_external
and dynamically load it rather than compiling it statically into httpd,
which would have
