Jesus, Ranger Admin log :-
Login Unsuccessful:rangerusersync | Ip Address:10.1.157.130 | Bad Credentials From CLI with ldapsearch is fine using :- ldapsearch -H ldaps://ldapbox.eset.corp -x -W -D "svc.sk.rangers...@eset.corp" -b "ou=eset,dc=eset,dc=corp" "(sAMAccountName="marc.hoppins")" Inside "install.properties" it is specified as: SYNC_LDAP_BIND_DN = CN=SVC.SK.rangerusersync,OU=System accounts,OU=SVC,OU=SK,OU=ESET,DC=eset,DC=corp -----Original Message----- From: Jesús Pérez <apa...@chuso.net> Sent: Wednesday, May 29, 2024 12:31 PM To: user@ranger.apache.org Subject: Re: Usersync EXTERNAL On Tue, May 28, 2024, at 11:00, Marc Hoppins wrote: > Ranger admin logs are unchanged from April. Thar's weird. Ranger Admin logs should at least be logging the API requests being sent from Usersync and Usersync is reporting it's getting an authentication error response from Ranger Admin, so that at least should be logged. Are you sure you are checking the correct logs? By default, in a vanilla installation the logs would go to ews/logs inside the Ranger Admin directory. You can also check ews/webapp/WEB-INF/classes/conf/logback.xml for any different logging configuration or the command line parameters with `ps ww -p $(sudo -u cat /var/run/ranger/rangeradmin.pid)` for any parameter that may have changed the logs location. You can even view the files that the Ranger Admin process has open to check for log files with: sudo -u ranger ls -l /proc/$(sudo -u ranger cat /var/run/ranger/rangeradmin.pid)/fd I find it very rare for an active Ranger Admin to have no logging activity for one month. Regards, Jesús P Rey
