Page 1 of 2
2015r2.0 LDAP woes
Posted: Wed Jul 15, 2015 8:27 pm
by vAJ
nls_login_success-failure.JPG
Was able to add LDAP server exactly as we have it setup in Netflow Analyzer (what I assume this feature was borrowed from) but logins are showing "success" but not allowing LDAP users in.
Ideas on where to look?
Re: 2015r2.0 LDAP woes
Posted: Wed Jul 15, 2015 9:07 pm
by Box293
I am getting the same behaviour as you, I did this on a freshly deployed VM.
Successfully added AD servers and imported users.
Trying to login just gives me Success.
We probably won't get a response from the USA techs until tomorrow.
Re: 2015r2.0 LDAP woes
Posted: Wed Jul 15, 2015 9:53 pm
by vAJ
Troy, can you open an internal bug request?
Re: 2015r2.0 LDAP woes
Posted: Wed Jul 15, 2015 10:15 pm
by Box293
I've let the techs know and tomorrow they will come back to us with what to do next. If a bug report needs to be filed they will do it.
Re: 2015r2.0 LDAP woes
Posted: Wed Jul 15, 2015 10:39 pm
by Box293
One other question, my tests were against a Windows Domain. Is your setup a Windows Domain or a non-Windows LDAP instance?
Re: 2015r2.0 LDAP woes
Posted: Thu Jul 16, 2015 9:11 am
by vAJ
Windows.
Re: 2015r2.0 LDAP woes
Posted: Thu Jul 16, 2015 9:22 am
by jomann
So the problem is when importing users it's missing a variable that is normally set when editing a user. In order to fix this for the time being if you edit the users you imported, make sure they are set to AD, the AD server you selected, and have the proper AD username in the username section and save the user you should be able to use it.
Working on a fix for the importing right now.
Re: 2015r2.0 LDAP woes
Posted: Thu Jul 16, 2015 9:44 am
by vAJ
Yep, mine are all missing the "AD Username". 40 users to correct, I'll go grab another cup of coffee...

Re: 2015r2.0 LDAP woes
Posted: Thu Jul 16, 2015 9:45 am
by vAJ
Also, my AD account is listed as an Admin, but when I login, no admin functions are visible.
Re: 2015r2.0 LDAP woes
Posted: Thu Jul 16, 2015 10:02 am
by jomann
It doesn't pull your authentication level based on the AD level - it's specifically set in Log Server when you do the import on the last page but you will have to go through and set the ones you want to be admins to admins if you didn't on the import page. Unless you mean it's set as admin in Log Server and not logging in with admin permissions?