/build/static/layout/Breadcrumb_cap_w.png

Application Setting Failed - Timed out on queue

Have been trying to enable ldap authentication on the K3000. We do not get a success message or the Green check mark. Using the User Login Test we receive a successfull message but AD authentication does not work. We are using the same 'working' settings from our K1 & K2 in regards to server/domain/username/password and have left the search filter blank.

 

Any suggestions would be appreciated.

 

Thanks


0 Comments   [ + ] Show comments

Answers (2)

Posted by: jknox 11 years ago
Red Belt
0

Are ports 389 or 636 open between the K3000 and the LDAP server?  LDAP may also have to be configured from the konfig admin account. 

I'm not sure on the konfig account. I've got a K3 VM, but haven't had much time to work with it yet.

Past that, I'd suggest opening a ticket with KACE support as the K3000 is still in beta at the moment.


Comments:
  • Thanks jknox. As authentication via AD or LDAP via AD isn't working the root account is the only one we can use. Yes, the appropriate ports are open to the ldap server as well. - jmarotto 11 years ago
    • Oops, yeah, I guess that would make sense. - jknox 11 years ago
Posted by: kendylp 11 years ago
Senior Yellow Belt
0

Beta support mentioned in passing an issue where authenticating as a user through LDAP often has to be done the first time using the user's full e-mail address as the user and the password associated with that account. AFTER that, the username works just fine. I have found that to be the case. when i've been enrolling devices, (even though i KNOW my ldap connector works) i could not use the user's credentials, but mine worked fine (thats another issue[i have several devices that arent mine that show as being mine] but if i use the user's e-mail address as the username and thier password, it works great... and thereafter just using that same user's AD username works.

Kendyl


Comments:
  • Kendyl,
    I posted a recap of that recommendation, along with some screen captures, at the following link: http://www.itninja.com/blog/view/k3000-ldap-authentication-first-login - Moncus 11 years ago
    • Very cool Moncus, MUCH more concise and understandable that my rambling above lol - kendylp 11 years ago
  • Thanks for the update. We did manage to get the LDAP connector working and can log in with user name. The Configuration page doesn't recognize this as Complete (no green check mark) but it works fine. My next challenge is. . .we have a need to have two active directory OUs connected. The K1 is setup to allow multiple LDAP connections. I do not find this on the K3. - jmarotto 11 years ago

Don't be a Stranger!

Sign up today to participate, stay informed, earn points and establish a reputation for yourself!

Sign up! or login

Share

 
This website uses cookies. By continuing to use this site and/or clicking the "Accept" button you are providing consent Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our websites or when you do business with us. For more information about our Privacy Policy and our data protection efforts, please visit GDPR-HQ