johnhenry

Thanks for your help, its greatly appreciated!

Brilliant!!!! Adding cn=Users under the DefaultLdapAuthoritiesPopulator bean appears to have solved the problem. I have added the working file to help anyone else if they are having any problems connecting Jasper Server 4 to a Microsoft Active Directory.

All logging modules have been turned on as suggested and the output created upon a login attempt (which ultimately failed of course) has been attached. (I haven't edited the log this time as I dont think they contain anything that could be a security risk as all.) Thank you by the way for your help. Post Edited by johnhenry at 05/09/2011 12:30

Surely if it finds the users full name (displayed immediately after the 'Getting authorities for user' log entries) then it has found the user in the active directory. Doesn't that mean that the initial credentials and user search are ok? Alas, the first and second suggestions you made didn't make any difference... Im about to turn on the extra logging and see if I can spot anything. I will post up a copy also.

Im having a few issues trying to get Active Directory integration working reliably in JasperServer 4 with our 2003 Windows domain using LDAP. I have managed to authenticate and log in before with the applicationContext-security.xml file I have attached. Though it seems that it is very intermittent. So far, out of around 100 login attempts, only a half a dozen or so have actually succeeded. (setting not changed between login attempts). The rest just return the error as shown in the attached log file. There are times when simple restarting the jasper services allows me to log in temporarily with AD authentication, but its very flakey. Does anyone have any ideas as to what might be causing such unreliable authentication?