Hello rbon Thank you very much for all the advice My case in version 6.0.4 works well.
Le mercredi 15 mai 2019 18:39:57 UTC+2, rbon a écrit : > > Alain, > > There are two connection errors in the log: > Error connecting to LDAP URL: ldap://ForestDnsZones.test.univ-bfc.fr:389 > Error connecting to LDAP URL: ldap://DomainDnsZones.test.univ-bfc.fr:389 > > Where do they come from? > Your config is pointing to 192.168.0.54! And this shows up in earlier log > entries. > Fix those errors first. > > In the logs, the bindDn is: > bindDn=cn=administrateur,cn=Users,dc=test,dc=univ-bfc,dc=fr > > but in your config it is: > bindDn cn = Administrator, cn = Users, dc = test, dc = univ-BFC, dc = com > > If the config you post is not the config you are using (that is, you are > changing the config you post, you run the risk of creating typos or > confusing the issue - such as the jumbled lines, e.g., cas.authn.ldap [0] > = false .useSsl) it makes finding the source of the problem(s) difficult. > Just copy and paste the config exactly as it is, then scrub passwords and > other sensitive data. > > As far as the failed log in (assuming it is not the result of the above > unknown ldap urls), choose a user in the search tree (again the two values > are different - posted config and log file output): > cas.authn.ldap [0] = .baseDn dc = test, dc = univ-CFB, dc = uk > > baseDn=dc=test,dc=univ-bfc,dc=fr > > Or do you have 'administrateur' in two places? (I would suggest against > having a bind user in the log in user tree, but that is a different > conversation.) > > > There are two other errors that show up. They should be dealt with later. > > 'An incompatible version [1.2.12] of the APR based Apache Tomcat Native > library' > > Seems like an included library conflict but does not look to affect CAS > operation. > > And a spring error: > > 'Error decoding flow execution' > > But again, CAS looks to be operating. > > Ray > > On Wed, 2019-05-15 at 10:34 +0200, alain ubfc wrote: > > Ray, > > Thank you for your answer. > > In fact we want the case to connect to the Active Directory. > I have an administrator account. > > Our applications are connected to AD. > Actually the error cas.authn.ldap[0].useSsl=false it's a copy / paste. > > I can access the interface of the case but I have an error identification > > [image: image.png] > > > I am attaching the log file. > > > Alain, > > It looks like CAS is making the connection to AD. Set log output to trace > to see if there are any more hints. Check AD logs (set them to debug at > least). > In your config, bindDn is 'Administrator' but in the output message it is > 'administrator'. > Does case matter for AD connections? > > The odd spacing and jumbled lines ('cas.authn.ldap [0] = false .useSsl' > should be 'cas.authn.ldap[0].useSsl = false') in your posted config may > indicate some hidden characters. > > Ray > > -- > > Ray Bon > Programmer Analyst > Development Services, University Systems > 2507218831 | CLE 019 | [email protected] <javascript:> > -- - Website: https://apereo.github.io/cas - Gitter Chatroom: https://gitter.im/apereo/cas - List Guidelines: https://goo.gl/1VRrw7 - Contributions: https://goo.gl/mh7qDG --- You received this message because you are subscribed to the Google Groups "CAS Community" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/a/apereo.org/d/msgid/cas-user/0f948747-9c69-49a8-b0a7-0569cd54288f%40apereo.org.
