Linux LDAP vs. Kerberos Authentication with Microsoft ActiveDirectory
Linux - SecurityThis forum is for all security related questions.
Questions, tips, system compromises, firewalls, etc. are all included here.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Linux LDAP vs. Kerberos Authentication with Microsoft ActiveDirectory
Hello all,,
i just wanted to consult you on which is better for authenticating Linux clients against Active Directory. LDAP or Kerberos agents??
let's discuss that in terms of pros and cons.
After some research and experimenting, I've come to the following:
Kerberos:
========
pros: 1) easy to set up 2) Encrypted authentication by default.
cons: hard-coding KDCs to bind to. This is a problem if all KDCs go down.
LDAP:
====
pros: N/A
cons: 1) requires server SSL certificate installed on clients in order to provide encrypted authentication.
Do you guys agree with this or have comments/advices?
Well you've got a bit of a gap here in that kerberos is ONLY for authentication, whereas LDAP will do both authentication AND user information. If you're going to use as the user infomation repository and access it via LDAP, then you'll have already done the "cons" work anyway. Where else would your users come from? Getting your own SSL certs really isn't exactly tricky either, and more self-reliant. One of the main benefits of kerberos is that it leads to the possibility of generic single sign on, which LDAP doesn't, as it only takes you as far as a generic one-shot credential check. Whilst it's simple to set up it can be confusing debugging KRB5 ticket statuses and such - per login LDAP worked or it didn't.
kerberos is easy to set up. but it can be a right bugger after that. I'm studying for my RHCA exams, and can't for the life of me work out why kpropd isn't working. DAMN YOU KERBEROS!!!
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.