You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@guacamole.apache.org by "Allugulapathi, Santhosh" <Sa...@anz.com.INVALID> on 2021/04/21 04:44:40 UTC
Apache Guacamole [Invalid Login] using AD LDAP
Hi Team,
We are using Apache Gucamole as a Bastion host solution and integrated with LDAPS, but when we try to login we are getting invalid login issue. There is no logging in var log messages about login failures. Also we have enabled DEBUG mode in log.xml under .gucamole but of no use as no messages are getting logged.
When we checked the developer tools below is the preview.
{message: "Invalid login",…}
* expected: [{name: "username", type: "USERNAME"}, {name: "password", type: "PASSWORD"}]
* message: "Invalid login"
* statusCode: null
* translatableMessage: {key: "APP.TEXT_UNTRANSLATED", variables: {MESSAGE: "Invalid login"}}
* type: "INVALID_CREDENTIALS"
Any help would be really appreciated.
Thanks
Santhosh
"This e-mail and any attachments to it (the "Communication") is, unless otherwise stated, confidential, may contain copyright material and is for the use only of the intended recipient. If you receive the Communication in error, please notify the sender immediately by return e-mail, delete the Communication and the return e-mail, and do not read, copy, retransmit or otherwise deal with it. Any views expressed in the Communication are those of the individual sender only, unless expressly stated to be those of Australia and New Zealand Banking Group Limited ABN 11 005 357 522, or any of its related entities including ANZ Bank New Zealand Limited (together "ANZ"). ANZ does not accept liability in connection with the integrity of or errors in the Communication, computer virus, data corruption, interference or delay arising from or in respect of the Communication."
Re: Apache Guacamole [Invalid Login] using AD LDAP
Posted by Mike Jumper <mi...@glyptodon.com>.
On Wed, Apr 21, 2021 at 8:02 AM Nick Couchman <vn...@apache.org> wrote:
> GUcamole version : guacamole-server-1.2.0
>>
>> Apache Tomcat/7.0.76
>>
>> Red Hat Enterprise Linux Server release 7.9 (Maipo)
>>
>> java version "1.8.0_281"
>>
>> Java(TM) SE Runtime Environment (build 8.0.6.25 -
>> pxa6480sr6fp25-20210115_01(SR6 FP25))
>>
>> IBM J9 VM (build 2.9, JRE 1.8.0 Linux amd64-64-Bit Compressed References
>> 20201218_462060 (JIT enabled, AOT enabled)
>>
>> OpenJ9 - 4c03b71
>>
>> OMR - 86a8e1a
>>
>> IBM - 8c30c56)
>>
>> JCL - 20210108_01 based on Oracle jdk8u281-b09
>>
>>
>>
>> Also I have checked the logs it is logging info messages but no login
>> failure messages. Also checked the catlina.out as well no logs.
>>
>>
>>
>> Checked in all possible locations but there are no authentication/failure
>> logs.
>>
>
> Next step would be to enable debug logging in Guacamole:
>
>
> http://guacamole.apache.org/doc/gug/configuring-guacamole.html#webapp-logging
>
> It's also important to know where your configuration is actually stored -
> you mentioned ".guacamole"; however, the default location has been
> /etc/guacamole for a couple of versions, so make sure you're aware of what
> location is actually in use. This could also contribute to errors - if the
> configuration is not in the correct location, it may not be reading the
> configuration at all.
>
Also, beware that Tomcat as currently packaged by RedHat, CentOS, Debian,
and others will not log to anything within /var/log/ nor catalina.out, but
rather to the systemd journal. The log messages you're looking for are
likely visible using journalctl.
Michael Jumper
CEO, Lead Developer
Glyptodon Inc <https://glyp.to/>.
Re: Apache Guacamole [Invalid Login] using AD LDAP
Posted by "Allugulapathi, Santhosh" <Sa...@anz.com.INVALID>.
Thanks Mike,
The binding of database,LDAP is fine and even the journalctl -u tomcat has the same entries aswell.
Apr 26 12:20:48 guac-host-2-0d3ba5 server: 12:20:48.684 [localhost-startStop-1] DEBUG o.a.g.extension.ExtensionModule - Loading extension: "guacamole-auth-jdbc-mysql-1.2.0.jar"
Apr 26 12:20:48 guac-host-2-0d3ba5 server: 12:20:48.803 [localhost-startStop-1] DEBUG o.a.g.extension.ExtensionModule - [0] Binding AuthenticationProvider "org.apache.guacamole.auth.mysql.MySQLAuthenticationProvider".
Apr 26 12:20:48 guac-host-2-0d3ba5 server: 12:20:48.833 [localhost-startStop-1] INFO o.a.g.environment.LocalEnvironment - GUACAMOLE_HOME is "/usr/share/tomcat/.guacamole".
Apr 26 12:20:49 guac-host-2-0d3ba5 server: 12:20:49.137 [localhost-startStop-1] DEBUG org.apache.ibatis.logging.LogFactory - Logging initialized using 'class org.apache.ibatis.logging.slf4j.Slf4jImpl' adapter.
Apr 26 12:20:51 guac-host-2-0d3ba5 server: 12:20:51.154 [localhost-startStop-1] DEBUG o.a.g.extension.ExtensionModule - [1] Binding AuthenticationProvider "org.apache.guacamole.auth.mysql.MySQLSharedAuthenticationProvider".
Apr 26 12:20:51 guac-host-2-0d3ba5 server: 12:20:51.454 [localhost-startStop-1] DEBUG o.a.g.extension.ExtensionModule - Loading extension: "guacamole-auth-ldap-1.2.0.jar"
Apr 26 12:20:51 guac-host-2-0d3ba5 server: 12:20:51.459 [localhost-startStop-1] DEBUG o.a.g.extension.ExtensionModule - [2] Binding AuthenticationProvider "org.apache.guacamole.auth.ldap.LDAPAuthenticationProvider".
Apr 26 12:20:51 guac-host-2-0d3ba5 server: 12:20:51.460 [localhost-startStop-1] INFO o.a.g.environment.LocalEnvironment - GUACAMOLE_HOME is "/usr/share/tomcat/.guacamole".
Apr 26 12:20:51 guac-host-2-0d3ba5 server: 12:20:51.848 [localhost-startStop-1] WARN o.a.g.e.LanguageResourceService - Overlay language resource "de" does not exist.
Apr 26 12:20:51 guac-host-2-0d3ba5 server: 12:20:51.851 [localhost-startStop-1] DEBUG o.a.g.e.LanguageResourceService - Merged strings with existing language: "en"
Apr 26 12:20:51 guac-host-2-0d3ba5 server: 12:20:51.851 [localhost-startStop-1] INFO o.a.g.extension.ExtensionModule - Extension "LDAP Authentication" loaded.
Apr 26 12:20:51 guac-host-2-0d3ba5 server: 12:20:51.852 [localhost-startStop-1] DEBUG o.a.g.extension.ExtensionModule - [3] Binding AuthenticationProvider "org.apache.guacamole.auth.file.FileAuthenticationProvider".
Apr 26 12:20:51 guac-host-2-0d3ba5 server: 12:20:51.853 [localhost-startStop-1] INFO o.a.g.environment.LocalEnvironment - GUACAMOLE_HOME is "/usr/share/tomcat/.guacamole".
Apr 26 12:20:52 guac-host-2-0d3ba5 server: 12:20:52.117 [localhost-startStop-1] INFO o.a.g.t.w.WebSocketTunnelModule - Loading JSR-356 WebSocket support...
Apr 26 12:20:52 guac-host-2-0d3ba5 server: 12:20:52.158 [localhost-startStop-1] DEBUG o.a.guacamole.tunnel.TunnelModule - WebSocket module loaded: org.apache.guacamole.tunnel.websocket.WebSocketTunnelModule
Regards,
Santhosh Allugulapathi | ANZ | Engineer - Cloud Services | Shared Services |
| ICS Domain |
| Ph +91 80 6795 6115 (Cisco Jabber)
Australia and New Zealand Banking Group Ltd | RMZ EcoWorld | Bengaluru |
P Please consider the environment before printing this email
From: Mike Jumper <mi...@glyptodon.com>
Reply to: "user@guacamole.apache.org" <us...@guacamole.apache.org>
Date: Sunday, 25 April 2021 at 6:48 AM
To: "user@guacamole.apache.org" <us...@guacamole.apache.org>
Subject: Re: Apache Guacamole [Invalid Login] using AD LDAP
As Nick mentioned, before going further, it's really critical to figure out where your logs are. They will be somewhere. In addition to messages noting the login failures, there will be messages noting the extensions that were successfully loaded, as well as relevant errors regarding things like certificate validation for LDAPS, the network connection to the database, etc. Lacking that information, guessing at possible causes will be counterproductive, as will making configuration changes based on those guesses.
If you're using the "tomcat" package installed directly from Red Hat's repository, it will be logging to the systemd journal. If you don't see logs there, I suggest re-checking - they should be there. For the standard "tomcat" package, you can narrow the output of journalctl to just messages from the relevant systemd unit:
journalctl -u tomcat
If you are not using the package from Red Hat's repository, you'll need to consult the documentation of the vendor providing your Tomcat package to find out where they put their logs.
Michael Jumper
CEO, Lead Developer
Glyptodon Inc<https://glyp.to/>.
On Thu, Apr 22, 2021 at 11:01 PM Allugulapathi, Santhosh <Sa...@anz.com.invalid> wrote:
We use the internal CA certificate and it is having a trusted certificate entry as below.
[root@guac-host-2-0d3ba5 jre]# keytool -list -keystore /usr/lib/jvm/java-1.8.0-ibm-1.8.0.6.25-1jpp.1.el7.x86_64/jre/lib/security/cacerts | grep anz
Enter keystore password:
***************** WARNING WARNING WARNING *****************
* The integrity of the information stored in the keystore *
* has NOT been verified! In order to verify its integrity, *
* you must provide the srckeystore password. *
***************** WARNING WARNING WARNING *****************
certv2, Feb 11, 2021, trustedCertEntry,
Below is snap of ps -ef | grep java. Is it having the correct configuration.
tomcat 17701 1 0 Apr20 ? 00:01:13 /usr/lib/jvm/jre/bin/java -Djavx.sql.DataSource.Factory=org.apache.commons.dbcp.BasicDataSourceFactory -classpath /usr/share/tomcat/bin/bootstrap.jar:/usr/share/tomcat/bin/tomcat-juli.jar:/usr/share/java/commons-daemon.jar -Dcatalina.base=/usr/share/tomcat -Dcatalina.home=/usr/share/tomcat -Djava.endorsed.dirs= -Djava.io.tmpdir=/var/cache/tomcat/temp -Djava.util.logging.config.file=/usr/share/tomcat/conf/logging.properties -Djava.util.logging.manager=org.apache.juli.ClassLoaderLogManager org.apache.catalina.startup.Bootstrap start
root 25899 25812 0 05:52 pts/0 00:00:00 grep --color=auto java
Thanks
Santhosh
From: Nick Couchman <vn...@apache.org>>
Reply to: "user@guacamole.apache.org<ma...@guacamole.apache.org>" <us...@guacamole.apache.org>>
Date: Thursday, 22 April 2021 at 11:21 PM
To: "user@guacamole.apache.org<ma...@guacamole.apache.org>" <us...@guacamole.apache.org>>
Subject: Re: Apache Guacamole [Invalid Login] using AD LDAP
On Wed, Apr 21, 2021 at 2:23 PM Allugulapathi, Santhosh <Sa...@anz.com.invalid> wrote:
It is pointing unidirectional quotes may be the mail format changed it , its OU="Service Accounts".
Try removing the quotes entirely - they really should not be needed.
Also, you mentioned earlier that you are using LDAPS - you need to make sure that the certificate for your LDAP server is trusted by Tomcat, which is usually done by adding it to the cacerts keystore for the version of Java that is running Tomcat, and then restarting Tomcat. My experience with LDAP servers and certificates is that they are usually either self-signed or signed by an internal CA (e.g. AD, eDirectory, etc.) and not by a globally trusted CA. This is also documented in the manual:
http://guacamole.apache.org/doc/gug/ldap-auth.html#guac-ldap-config
Checked the journalctl logs no messages are getting logged in it aswell. Tried to login into guacamole using both LDAP aswell as gucaadmin but no loggings are happening.
You really need to determine where the logs are going on your system - that will be the key to figuring out why authentication is failing.
-Nick
"This e-mail and any attachments to it (the "Communication") is, unless otherwise stated, confidential, may contain copyright material and is for the use only of the intended recipient. If you receive the Communication in error, please notify the sender immediately by return e-mail, delete the Communication and the return e-mail, and do not read, copy, retransmit or otherwise deal with it. Any views expressed in the Communication are those of the individual sender only, unless expressly stated to be those of Australia and New Zealand Banking Group Limited ABN 11 005 357 522, or any of its related entities including ANZ Bank New Zealand Limited (together "ANZ"). ANZ does not accept liability in connection with the integrity of or errors in the Communication, computer virus, data corruption, interference or delay arising from or in respect of the Communication."
"This e-mail and any attachments to it (the "Communication") is, unless otherwise stated, confidential, may contain copyright material and is for the use only of the intended recipient. If you receive the Communication in error, please notify the sender immediately by return e-mail, delete the Communication and the return e-mail, and do not read, copy, retransmit or otherwise deal with it. Any views expressed in the Communication are those of the individual sender only, unless expressly stated to be those of Australia and New Zealand Banking Group Limited ABN 11 005 357 522, or any of its related entities including ANZ Bank New Zealand Limited (together "ANZ"). ANZ does not accept liability in connection with the integrity of or errors in the Communication, computer virus, data corruption, interference or delay arising from or in respect of the Communication."
---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscribe@guacamole.apache.org
For additional commands, e-mail: user-help@guacamole.apache.org
Re: Apache Guacamole [Invalid Login] using AD LDAP
Posted by Mike Jumper <mi...@glyptodon.com>.
As Nick mentioned, before going further, it's really critical to figure out
where your logs are. They will be somewhere. In addition to messages noting
the login failures, there will be messages noting the extensions that were
successfully loaded, as well as relevant errors regarding things like
certificate validation for LDAPS, the network connection to the database,
etc. Lacking that information, guessing at possible causes will be
counterproductive, as will making configuration changes based on those
guesses.
If you're using the "tomcat" package installed directly from Red Hat's
repository, it will be logging to the systemd journal. If you don't see
logs there, I suggest re-checking - they should be there. For the standard
"tomcat" package, you can narrow the output of journalctl to just messages
from the relevant systemd unit:
journalctl -u tomcat
If you are not using the package from Red Hat's repository, you'll need to
consult the documentation of the vendor providing your Tomcat package to
find out where they put their logs.
Michael Jumper
CEO, Lead Developer
Glyptodon Inc <https://glyp.to/>.
On Thu, Apr 22, 2021 at 11:01 PM Allugulapathi, Santhosh
<Sa...@anz.com.invalid> wrote:
> We use the internal CA certificate and it is having a trusted certificate
> entry as below.
>
>
>
> [root@guac-host-2-0d3ba5 jre]# keytool -list -keystore
> /usr/lib/jvm/java-1.8.0-ibm-1.8.0.6.25-1jpp.1.el7.x86_64/jre/lib/security/cacerts
> | grep anz
>
> Enter keystore password:
>
>
>
> ***************** WARNING WARNING WARNING *****************
>
> * The integrity of the information stored in the keystore *
>
> * has NOT been verified! In order to verify its integrity, *
>
> * you must provide the srckeystore password. *
>
> ***************** WARNING WARNING WARNING *****************
>
>
>
> certv2, Feb 11, 2021, trustedCertEntry,
>
>
>
> Below is snap of ps -ef | grep java. Is it having the correct
> configuration.
>
>
>
> tomcat 17701 1 0 Apr20 ? 00:01:13 /usr/lib/jvm/jre/bin/java
> -Djavx.sql.DataSource.Factory=org.apache.commons.dbcp.BasicDataSourceFactory
> -classpath
> /usr/share/tomcat/bin/bootstrap.jar:/usr/share/tomcat/bin/tomcat-juli.jar:/usr/share/java/commons-daemon.jar
> -Dcatalina.base=/usr/share/tomcat -Dcatalina.home=/usr/share/tomcat
> -Djava.endorsed.dirs= -Djava.io.tmpdir=/var/cache/tomcat/temp
> -Djava.util.logging.config.file=/usr/share/tomcat/conf/logging.properties
> -Djava.util.logging.manager=org.apache.juli.ClassLoaderLogManager
> org.apache.catalina.startup.Bootstrap start
>
> root 25899 25812 0 05:52 pts/0 00:00:00 grep --color=auto java
>
> Thanks
> Santhosh
>
> From: Nick Couchman <vn...@apache.org>
> Reply to: "user@guacamole.apache.org" <us...@guacamole.apache.org>
> Date: Thursday, 22 April 2021 at 11:21 PM
> To: "user@guacamole.apache.org" <us...@guacamole.apache.org>
> Subject: Re: Apache Guacamole [Invalid Login] using AD LDAP
>
> On Wed, Apr 21, 2021 at 2:23 PM Allugulapathi, Santhosh
> <Sa...@anz.com.invalid> wrote:
> It is pointing unidirectional quotes may be the mail format changed it ,
> its OU="Service Accounts".
>
> Try removing the quotes entirely - they really should not be needed.
>
> Also, you mentioned earlier that you are using LDAPS - you need to make
> sure that the certificate for your LDAP server is trusted by Tomcat, which
> is usually done by adding it to the cacerts keystore for the version of
> Java that is running Tomcat, and then restarting Tomcat. My experience with
> LDAP servers and certificates is that they are usually either self-signed
> or signed by an internal CA (e.g. AD, eDirectory, etc.) and not by a
> globally trusted CA. This is also documented in the manual:
> http://guacamole.apache.org/doc/gug/ldap-auth.html#guac-ldap-config
>
>
> Checked the journalctl logs no messages are getting logged in it aswell.
> Tried to login into guacamole using both LDAP aswell as gucaadmin but no
> loggings are happening.
>
> You really need to determine where the logs are going on your system -
> that will be the key to figuring out why authentication is failing.
>
> -Nick
> "This e-mail and any attachments to it (the "Communication") is, unless
> otherwise stated, confidential, may contain copyright material and is for
> the use only of the intended recipient. If you receive the Communication in
> error, please notify the sender immediately by return e-mail, delete the
> Communication and the return e-mail, and do not read, copy, retransmit or
> otherwise deal with it. Any views expressed in the Communication are those
> of the individual sender only, unless expressly stated to be those of
> Australia and New Zealand Banking Group Limited ABN 11 005 357 522, or any
> of its related entities including ANZ Bank New Zealand Limited (together
> "ANZ"). ANZ does not accept liability in connection with the integrity of
> or errors in the Communication, computer virus, data corruption,
> interference or delay arising from or in respect of the Communication."
>
Re: Apache Guacamole [Invalid Login] using AD LDAP
Posted by "Allugulapathi, Santhosh" <Sa...@anz.com.INVALID>.
We use the internal CA certificate and it is having a trusted certificate entry as below.
[root@guac-host-2-0d3ba5 jre]# keytool -list -keystore /usr/lib/jvm/java-1.8.0-ibm-1.8.0.6.25-1jpp.1.el7.x86_64/jre/lib/security/cacerts | grep anz
Enter keystore password:
***************** WARNING WARNING WARNING *****************
* The integrity of the information stored in the keystore *
* has NOT been verified! In order to verify its integrity, *
* you must provide the srckeystore password. *
***************** WARNING WARNING WARNING *****************
certv2, Feb 11, 2021, trustedCertEntry,
Below is snap of ps -ef | grep java. Is it having the correct configuration.
tomcat 17701 1 0 Apr20 ? 00:01:13 /usr/lib/jvm/jre/bin/java -Djavx.sql.DataSource.Factory=org.apache.commons.dbcp.BasicDataSourceFactory -classpath /usr/share/tomcat/bin/bootstrap.jar:/usr/share/tomcat/bin/tomcat-juli.jar:/usr/share/java/commons-daemon.jar -Dcatalina.base=/usr/share/tomcat -Dcatalina.home=/usr/share/tomcat -Djava.endorsed.dirs= -Djava.io.tmpdir=/var/cache/tomcat/temp -Djava.util.logging.config.file=/usr/share/tomcat/conf/logging.properties -Djava.util.logging.manager=org.apache.juli.ClassLoaderLogManager org.apache.catalina.startup.Bootstrap start
root 25899 25812 0 05:52 pts/0 00:00:00 grep --color=auto java
Thanks
Santhosh
From: Nick Couchman <vn...@apache.org>
Reply to: "user@guacamole.apache.org" <us...@guacamole.apache.org>
Date: Thursday, 22 April 2021 at 11:21 PM
To: "user@guacamole.apache.org" <us...@guacamole.apache.org>
Subject: Re: Apache Guacamole [Invalid Login] using AD LDAP
On Wed, Apr 21, 2021 at 2:23 PM Allugulapathi, Santhosh <Sa...@anz.com.invalid> wrote:
It is pointing unidirectional quotes may be the mail format changed it , its OU="Service Accounts".
Try removing the quotes entirely - they really should not be needed.
Also, you mentioned earlier that you are using LDAPS - you need to make sure that the certificate for your LDAP server is trusted by Tomcat, which is usually done by adding it to the cacerts keystore for the version of Java that is running Tomcat, and then restarting Tomcat. My experience with LDAP servers and certificates is that they are usually either self-signed or signed by an internal CA (e.g. AD, eDirectory, etc.) and not by a globally trusted CA. This is also documented in the manual:
http://guacamole.apache.org/doc/gug/ldap-auth.html#guac-ldap-config
Checked the journalctl logs no messages are getting logged in it aswell. Tried to login into guacamole using both LDAP aswell as gucaadmin but no loggings are happening.
You really need to determine where the logs are going on your system - that will be the key to figuring out why authentication is failing.
-Nick
"This e-mail and any attachments to it (the "Communication") is, unless otherwise stated, confidential, may contain copyright material and is for the use only of the intended recipient. If you receive the Communication in error, please notify the sender immediately by return e-mail, delete the Communication and the return e-mail, and do not read, copy, retransmit or otherwise deal with it. Any views expressed in the Communication are those of the individual sender only, unless expressly stated to be those of Australia and New Zealand Banking Group Limited ABN 11 005 357 522, or any of its related entities including ANZ Bank New Zealand Limited (together "ANZ"). ANZ does not accept liability in connection with the integrity of or errors in the Communication, computer virus, data corruption, interference or delay arising from or in respect of the Communication."
Re: Apache Guacamole [Invalid Login] using AD LDAP
Posted by Nick Couchman <vn...@apache.org>.
On Wed, Apr 21, 2021 at 2:23 PM Allugulapathi, Santhosh
<Sa...@anz.com.invalid> wrote:
> It is pointing unidirectional quotes may be the mail format changed it ,
> its OU="Service Accounts".
>
>
Try removing the quotes entirely - they really should not be needed.
Also, you mentioned earlier that you are using LDAPS - you need to make
sure that the certificate for your LDAP server is trusted by Tomcat, which
is usually done by adding it to the cacerts keystore for the version of
Java that is running Tomcat, and then restarting Tomcat. My experience with
LDAP servers and certificates is that they are usually either self-signed
or signed by an internal CA (e.g. AD, eDirectory, etc.) and not by a
globally trusted CA. This is also documented in the manual:
http://guacamole.apache.org/doc/gug/ldap-auth.html#guac-ldap-config
>
> Checked the journalctl logs no messages are getting logged in it aswell.
> Tried to login into guacamole using both LDAP aswell as gucaadmin but no
> loggings are happening.
>
>
You really need to determine where the logs are going on your system - that
will be the key to figuring out why authentication is failing.
-Nick
Re: Apache Guacamole [Invalid Login] using AD LDAP
Posted by "Allugulapathi, Santhosh" <Sa...@anz.com.INVALID>.
Tried to disable SELinux but no use aswell no logging in the logs aswell. Any other suggestion please.
SELinux status: enabled
SELinuxfs mount: /sys/fs/selinux
SELinux root directory: /etc/selinux
Loaded policy name: targeted
Current mode: permissive
Mode from config file: enforcing
Policy MLS status: enabled
Policy deny_unknown status: allowed
Max kernel policy version: 31
Thanks
Santhosh
From: Santhosh Allugulapathi <Sa...@anz.com>
Date: Wednesday, 21 April 2021 at 11:47 PM
To: "user@guacamole.apache.org" <us...@guacamole.apache.org>
Subject: Re: Apache Guacamole [Invalid Login] using AD LDAP
It is pointing unidirectional quotes may be the mail format changed it , its OU="Service Accounts".
Checked the journalctl logs no messages are getting logged in it aswell. Tried to login into guacamole using both LDAP aswell as gucaadmin but no loggings are happening.
Thanks
Santhosh
From: Nick Couchman <vn...@apache.org>
Reply to: "user@guacamole.apache.org" <us...@guacamole.apache.org>
Date: Wednesday, 21 April 2021 at 11:35 PM
To: "user@guacamole.apache.org" <us...@guacamole.apache.org>
Subject: Re: Apache Guacamole [Invalid Login] using AD LDAP
...
ldap-search-bind-dn: CN=User,OU=“Service Accounts”,OU=Security,DC=glbl,DC=bnv,DC=com
...
The above uses directional double quotes (U+201C and U+201D) rather than the normal non-directional double quote (U+0022). This might just be because your email client is trying to make things pretty, but it's worth checking that the same isn't in your guacamole.properties. I don't think the directional quotes will have the same meaning to software expecting double-quoted values, including LDAP servers.
Also, I don't think Guacamole requires that you quote spaces in the configuration file, which is, I assume, why the quotes are in there. My configuration that uses LDAP has a space in the OU, and I don't have any trouble with the space and don't use quotes.
-Nick
"This e-mail and any attachments to it (the "Communication") is, unless otherwise stated, confidential, may contain copyright material and is for the use only of the intended recipient. If you receive the Communication in error, please notify the sender immediately by return e-mail, delete the Communication and the return e-mail, and do not read, copy, retransmit or otherwise deal with it. Any views expressed in the Communication are those of the individual sender only, unless expressly stated to be those of Australia and New Zealand Banking Group Limited ABN 11 005 357 522, or any of its related entities including ANZ Bank New Zealand Limited (together "ANZ"). ANZ does not accept liability in connection with the integrity of or errors in the Communication, computer virus, data corruption, interference or delay arising from or in respect of the Communication."
Re: Apache Guacamole [Invalid Login] using AD LDAP
Posted by "Allugulapathi, Santhosh" <Sa...@anz.com.INVALID>.
It is pointing unidirectional quotes may be the mail format changed it , its OU="Service Accounts".
Checked the journalctl logs no messages are getting logged in it aswell. Tried to login into guacamole using both LDAP aswell as gucaadmin but no loggings are happening.
Regards,
Santhosh Allugulapathi | ANZ | Engineer - Cloud Services | Shared Services |
| ICS Domain |
| Ph +91 80 6795 6115 (Cisco Jabber)
Australia and New Zealand Banking Group Ltd | RMZ EcoWorld | Bengaluru |
P Please consider the environment before printing this email
From: Nick Couchman <vn...@apache.org>
Reply to: "user@guacamole.apache.org" <us...@guacamole.apache.org>
Date: Wednesday, 21 April 2021 at 11:35 PM
To: "user@guacamole.apache.org" <us...@guacamole.apache.org>
Subject: Re: Apache Guacamole [Invalid Login] using AD LDAP
...
ldap-search-bind-dn: CN=User,OU=“Service Accounts”,OU=Security,DC=glbl,DC=bnv,DC=com
...
The above uses directional double quotes (U+201C and U+201D) rather than the normal non-directional double quote (U+0022). This might just be because your email client is trying to make things pretty, but it's worth checking that the same isn't in your guacamole.properties. I don't think the directional quotes will have the same meaning to software expecting double-quoted values, including LDAP servers.
Also, I don't think Guacamole requires that you quote spaces in the configuration file, which is, I assume, why the quotes are in there. My configuration that uses LDAP has a space in the OU, and I don't have any trouble with the space and don't use quotes.
-Nick
"This e-mail and any attachments to it (the "Communication") is, unless otherwise stated, confidential, may contain copyright material and is for the use only of the intended recipient. If you receive the Communication in error, please notify the sender immediately by return e-mail, delete the Communication and the return e-mail, and do not read, copy, retransmit or otherwise deal with it. Any views expressed in the Communication are those of the individual sender only, unless expressly stated to be those of Australia and New Zealand Banking Group Limited ABN 11 005 357 522, or any of its related entities including ANZ Bank New Zealand Limited (together "ANZ"). ANZ does not accept liability in connection with the integrity of or errors in the Communication, computer virus, data corruption, interference or delay arising from or in respect of the Communication."
Re: Apache Guacamole [Invalid Login] using AD LDAP
Posted by Nick Couchman <vn...@apache.org>.
>
>
>> ...
>> ldap-search-bind-dn: CN=User,OU=“Service
>> Accounts”,OU=Security,DC=glbl,DC=bnv,DC=com
>> ...
>
>
> The above uses directional double quotes (U+201C and U+201D) rather than
> the normal non-directional double quote (U+0022). This might just be
> because your email client is trying to make things pretty, but it's worth
> checking that the same isn't in your guacamole.properties. I don't think
> the directional quotes will have the same meaning to software expecting
> double-quoted values, including LDAP servers.
>
>
Also, I don't think Guacamole requires that you quote spaces in the
configuration file, which is, I assume, why the quotes are in there. My
configuration that uses LDAP has a space in the OU, and I don't have any
trouble with the space and don't use quotes.
-Nick
Re: Apache Guacamole [Invalid Login] using AD LDAP
Posted by Mike Jumper <mi...@glyptodon.com>.
On Wed, Apr 21, 2021 at 10:49 AM Allugulapathi, Santhosh
<Sa...@anz.com.invalid> wrote:
> ...
> Also we are using /usr/share/tomcat/.guacamole/guacamole.properties as the
> guacamole directory and below is a Snap of Gucamole Properties file
>
This will be fine so long as "/usr/share/tomcat/" is the home directory of
the Tomcat service user. If not, or if unsure, it would be better to just
use "/etc/guacamole".
...
> auth-provider: net.sourceforge.guacamole.net
> .auth.ldap.LDAPAuthenticationProvider
> auth-provider: net.sourceforge.guacamole.net
> .auth.mysql.MySQLAuthenticationProvider
>
This will not be the cause of any failure, but be advised that there is no
"auth-provider" property, and there hasn't been one for years. It was
removed some time ago in favor of a self-contained extension format. These
properties have no meaning to Guacamole and will be ignored.
There should be quite a bit of log information from Guacamole during
startup and from the LDAP extension, assuming things are in the correct
locations. As distro-packaged versions of Tomcat tend to use the systemd
journal, please check journalctl to see if the logs are there.
...
> ldap-search-bind-dn: CN=User,OU=“Service
> Accounts”,OU=Security,DC=glbl,DC=bnv,DC=com
> ...
The above uses directional double quotes (U+201C and U+201D) rather than
the normal non-directional double quote (U+0022). This might just be
because your email client is trying to make things pretty, but it's worth
checking that the same isn't in your guacamole.properties. I don't think
the directional quotes will have the same meaning to software expecting
double-quoted values, including LDAP servers.
Michael Jumper
CEO, Lead Developer
Glyptodon Inc <https://glyp.to/>.
Re: Apache Guacamole [Invalid Login] using AD LDAP
Posted by "Allugulapathi, Santhosh" <Sa...@anz.com.INVALID>.
Hi Nick,
We have already configured Debug in logback.xml as below
<configuration>
<!-- Default appender -->
<appender name="GUAC-DEFAULT" class="ch.qos.logback.core.ConsoleAppender">
<encoder>
<pattern>%d{HH:mm:ss.SSS} [%thread] %-5level %logger{36} - %msg%n</pattern>
</encoder>
</appender>
<!-- Log at DEBUG level -->
<root level="debug">
<appender-ref ref="GUAC-DEBUG" />
</root>
</configuration>
Also we are using /usr/share/tomcat/.guacamole/guacamole.properties as the guacamole directory and below is a Snap of Gucamole Properties file
guacd-hostname: localhost
guacd-port: 4822
auth-provider: net.sourceforge.guacamole.net.auth.ldap.LDAPAuthenticationProvider
auth-provider: net.sourceforge.guacamole.net.auth.mysql.MySQLAuthenticationProvider
mysql-hostname: 10.19.1.25
mysql-port: 3306
mysql-database: guacamole
mysql-username: guacadmin
mysql-password: ***********************
mysql-default-max-connections-per-user: 5
mysql-default-max-group-connections-per-user: 5
# LDAP properties
ldap-hostname: ldaps.glbl.bnv.com
ldap-port: 636
ldap-encryption-method: ssl
ldap-search-bind-dn: CN=User,OU=“Service Accounts”,OU=Security,DC=glbl,DC=bnv,DC=com
ldap-search-bind-password: ********************
ldap-user-base-dn: DC=glbl,DC=bnv,DC=com
ldap-username-attribute: sAMAccountName
ldap-user-search-filter: (memberOf=CN=GLBL PROCESS MODELLING,OU=Common,OU=Groups,DC=glbl,DC=bnv,DC=com)
there is a space between service and accounts so used double quotes.
Thanks
Santhosh
From: Nick Couchman <vn...@apache.org>
Reply to: "user@guacamole.apache.org" <us...@guacamole.apache.org>
Date: Wednesday, 21 April 2021 at 8:33 PM
To: "user@guacamole.apache.org" <us...@guacamole.apache.org>
Subject: Re: Apache Guacamole [Invalid Login] using AD LDAP
GUcamole version : guacamole-server-1.2.0
Apache Tomcat/7.0.76
Red Hat Enterprise Linux Server release 7.9 (Maipo)
java version "1.8.0_281"
Java(TM) SE Runtime Environment (build 8.0.6.25 - pxa6480sr6fp25-20210115_01(SR6 FP25))
IBM J9 VM (build 2.9, JRE 1.8.0 Linux amd64-64-Bit Compressed References 20201218_462060 (JIT enabled, AOT enabled)
OpenJ9 - 4c03b71
OMR - 86a8e1a
IBM - 8c30c56)
JCL - 20210108_01 based on Oracle jdk8u281-b09
Also I have checked the logs it is logging info messages but no login failure messages. Also checked the catlina.out as well no logs.
Checked in all possible locations but there are no authentication/failure logs.
Next step would be to enable debug logging in Guacamole:
http://guacamole.apache.org/doc/gug/configuring-guacamole.html#webapp-logging
It's also important to know where your configuration is actually stored - you mentioned ".guacamole"; however, the default location has been /etc/guacamole for a couple of versions, so make sure you're aware of what location is actually in use. This could also contribute to errors - if the configuration is not in the correct location, it may not be reading the configuration at all.
-Nick
"This e-mail and any attachments to it (the "Communication") is, unless otherwise stated, confidential, may contain copyright material and is for the use only of the intended recipient. If you receive the Communication in error, please notify the sender immediately by return e-mail, delete the Communication and the return e-mail, and do not read, copy, retransmit or otherwise deal with it. Any views expressed in the Communication are those of the individual sender only, unless expressly stated to be those of Australia and New Zealand Banking Group Limited ABN 11 005 357 522, or any of its related entities including ANZ Bank New Zealand Limited (together "ANZ"). ANZ does not accept liability in connection with the integrity of or errors in the Communication, computer virus, data corruption, interference or delay arising from or in respect of the Communication."
Re: Apache Guacamole [Invalid Login] using AD LDAP
Posted by Nick Couchman <vn...@apache.org>.
>
> GUcamole version : guacamole-server-1.2.0
>
> Apache Tomcat/7.0.76
>
> Red Hat Enterprise Linux Server release 7.9 (Maipo)
>
> java version "1.8.0_281"
>
> Java(TM) SE Runtime Environment (build 8.0.6.25 -
> pxa6480sr6fp25-20210115_01(SR6 FP25))
>
> IBM J9 VM (build 2.9, JRE 1.8.0 Linux amd64-64-Bit Compressed References
> 20201218_462060 (JIT enabled, AOT enabled)
>
> OpenJ9 - 4c03b71
>
> OMR - 86a8e1a
>
> IBM - 8c30c56)
>
> JCL - 20210108_01 based on Oracle jdk8u281-b09
>
>
>
> Also I have checked the logs it is logging info messages but no login
> failure messages. Also checked the catlina.out as well no logs.
>
>
>
> Checked in all possible locations but there are no authentication/failure
> logs.
>
Next step would be to enable debug logging in Guacamole:
http://guacamole.apache.org/doc/gug/configuring-guacamole.html#webapp-logging
It's also important to know where your configuration is actually stored -
you mentioned ".guacamole"; however, the default location has been
/etc/guacamole for a couple of versions, so make sure you're aware of what
location is actually in use. This could also contribute to errors - if the
configuration is not in the correct location, it may not be reading the
configuration at all.
-Nick
Re: Apache Guacamole [Invalid Login] using AD LDAP
Posted by "Allugulapathi, Santhosh" <Sa...@anz.com.INVALID>.
Thanks Nick for coming back.
Please find the details
GUcamole version : guacamole-server-1.2.0
Apache Tomcat/7.0.76
Red Hat Enterprise Linux Server release 7.9 (Maipo)
java version "1.8.0_281"
Java(TM) SE Runtime Environment (build 8.0.6.25 - pxa6480sr6fp25-20210115_01(SR6 FP25))
IBM J9 VM (build 2.9, JRE 1.8.0 Linux amd64-64-Bit Compressed References 20201218_462060 (JIT enabled, AOT enabled)
OpenJ9 - 4c03b71
OMR - 86a8e1a
IBM - 8c30c56)
JCL - 20210108_01 based on Oracle jdk8u281-b09
Also I have checked the logs it is logging info messages but no login failure messages. Also checked the catlina.out as well no logs.
Checked in all possible locations but there are no authentication/failure logs.
Regards,
Santhosh Allugulapathi | ANZ | Engineer - Cloud Services | Shared Services |
| ICS Domain |
| Ph +91 80 6795 6115 (Cisco Jabber)
Australia and New Zealand Banking Group Ltd | RMZ EcoWorld | Bengaluru |
P Please consider the environment before printing this email
From: Nick Couchman <vn...@apache.org>
Reply to: "user@guacamole.apache.org" <us...@guacamole.apache.org>
Date: Wednesday, 21 April 2021 at 4:51 PM
To: "user@guacamole.apache.org" <us...@guacamole.apache.org>
Subject: Re: Apache Guacamole [Invalid Login] using AD LDAP
On Wed, Apr 21, 2021 at 12:47 AM Allugulapathi, Santhosh <Sa...@anz.com.invalid> wrote:
Hi Team,
We are using Apache Gucamole as a Bastion host solution and integrated with LDAPS, but when we try to login we are getting invalid login issue. There is no logging in var log messages about login failures. Also we have enabled DEBUG mode in log.xml under .gucamole but of no use as no messages are getting logged.
What version of Guacamole? What is the install environment (O/S, Tomcat and Java versions, etc.)? Tomcat may not be logging to /var/log/messages - in some situations it does, however, in many situations there is a specific Tomcat log file. If you are seeing absolutely no messages related to Tomcat or Guacamole, then you're probably looking in the wrong place. Locate the Tomcat log file (often catalina.out) and see if any messages show up there.
-Nick
"This e-mail and any attachments to it (the "Communication") is, unless otherwise stated, confidential, may contain copyright material and is for the use only of the intended recipient. If you receive the Communication in error, please notify the sender immediately by return e-mail, delete the Communication and the return e-mail, and do not read, copy, retransmit or otherwise deal with it. Any views expressed in the Communication are those of the individual sender only, unless expressly stated to be those of Australia and New Zealand Banking Group Limited ABN 11 005 357 522, or any of its related entities including ANZ Bank New Zealand Limited (together "ANZ"). ANZ does not accept liability in connection with the integrity of or errors in the Communication, computer virus, data corruption, interference or delay arising from or in respect of the Communication."
---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscribe@guacamole.apache.org
For additional commands, e-mail: user-help@guacamole.apache.org
Re: Apache Guacamole [Invalid Login] using AD LDAP
Posted by Nick Couchman <vn...@apache.org>.
On Wed, Apr 21, 2021 at 12:47 AM Allugulapathi, Santhosh
<Sa...@anz.com.invalid> wrote:
>
> Hi Team,
>
> We are using Apache Gucamole as a Bastion host solution and integrated
> with LDAPS, but when we try to login we are getting invalid login issue.
> There is no logging in var log messages about login failures. Also we have
> enabled DEBUG mode in log.xml under .gucamole but of no use as no messages
> are getting logged.
>
>
What version of Guacamole? What is the install environment (O/S, Tomcat and
Java versions, etc.)? Tomcat may not be logging to /var/log/messages - in
some situations it does, however, in many situations there is a specific
Tomcat log file. If you are seeing absolutely no messages related to Tomcat
or Guacamole, then you're probably looking in the wrong place. Locate the
Tomcat log file (often catalina.out) and see if any messages show up there.
-Nick