RE: LDAP Guacamole 9.14

2018-02-05 Thread Ferron Nijland - Switch IT Solutions
: Mike Jumper [mailto:mike.jum...@guac-dev.org] Verzonden: vrijdag 2 februari 2018 18:29 Aan: user@guacamole.apache.org Onderwerp: Re: LDAP Guacamole 9.14 On Fri, Feb 2, 2018 at 5:25 AM, Ferron Nijland - Switch IT Solutions mailto:f.nijl...@switch.nl>> wrote: Hello Everyone, Hello Ferron,

Re: LDAP Guacamole 9.14

2018-02-02 Thread Nick Couchman
> > I also noticed that your running LDAP on port 3268. That's not the port > that LDAP usually runs on, did you double check that your LDAP server is > really running on port 3268? > > Port 3268 is standard when running Active Directory - it is the global catalog port. There was a referral bug in

Re: LDAP Guacamole 9.14

2018-02-02 Thread Aaron Newsome
Hello Ferron. I've got 0.9.14 running with LDAP authentication. I've actually used an identical config since 0.9.12 without any problems. Here's the LDAP section of my guacamole.properties file: ldap-hostname: ads-001.swiftlab.local ldap-port: 389 ldap-max-search-results: 3000 ldap-search-bind-

Re: LDAP Guacamole 9.14

2018-02-02 Thread Nick Couchman
On Fri, Feb 2, 2018 at 5:00 PM, Jerry wrote: > For what it's worth, using ldap-username-attribute sAMAccountname never > worked for me on 0.9.13-incubating (though it seemed to work for other > people based on my googling), but CN worked fine. > I have no issue with using sAMAccountName against

Re: LDAP Guacamole 9.14

2018-02-02 Thread Jerry
For what it's worth, using ldap-username-attribute sAMAccountname never worked for me on 0.9.13-incubating (though it seemed to work for other people based on my googling), but CN worked fine. -- Sent from: http://apache-guacamole-general-user-mailing-list.2363388.n4.nabble.com/

Re: LDAP Guacamole 9.14

2018-02-02 Thread Mike Jumper
On Fri, Feb 2, 2018 at 5:25 AM, Ferron Nijland - Switch IT Solutions < f.nijl...@switch.nl> wrote: > Hello Everyone, > > > Hello Ferron, I’ve installed a new installation of Guacamole 9.14. > > I can access the GUI and login with sql authentication. > > Now I’ve added LDAP authentication, but it