4 ms·
Ad "LDAP/AD integration": > This is actually a regular request of Canonical's corporate Ubuntu Desktop customers. We're generally able to meet the needs of ou
by mschuster91 10y ago
Ad "LDAP/AD integration":
> This is actually a regular request of Canonical's corporate Ubuntu Desktop customers. We're generally able to meet the needs of our enterprise customers around LDAP and ActiveDirectory authentication. We'll look at what else we can do natively in the distro to improve this.
OK I get the need that some may have to integrate an UI but please don't ship a full-blown Samba/winbindd plus config generator as default.
Here's the why:
Everyone has different LDAP setups. Some use a homegrown LDAP, some use MS AD in varying versions, some use Samba as AD in varying versions - and then everyone uses a different LDAP/AD scheme (e.g. is the username attribute lowercase-able, which attribute is it mapped to, are all PCs/users in a single OU, do you want to restrict logins to specific groups, does the organization need "full" AD setup or will a plain ldap_bind be sufficient ...) and you almost always need to hand-tune the configuration for your specific setup. A GUI configurator will most likely only work OOTB for people sticking with a standard MS AD, and make problems with non-standard setups, multi-domain memberships or similar.
And: Non-enterprise users will most likely not need AD/LDAP support. Those who do should have competent admins anyhow, but what I can certainly say is that the documentation could be updated (e.g. https://wiki.ubuntuusers.de/Samba_Winbind/ https://wiki.ubuntuusers.de/Samba_Winbind/ only works for 12.04/14.04). I'd rather like if the documentation were improved than yet another shoddy Samba config generator that's falling out of sync with Samba more sooner than later...
(source: lost more than a few hairs wrestling with AD and LDAP)
- ansible 10y agoAnd: Non-enterprise users will most likely not need AD/LDAP support. I strongly disagree with this. Everyone with more than 2 users in their organization can benefit from AD/LDAP support, if it is easy to set up and administer. Because... what else is viable for managing multiple user accounts across several machines? Twenty years ago, I would have said NIS (from Sun, originally called YP for 'yellowpages'). But that was horribly insecure. NIS+ was supposed to fix that, but support was never there in Linux land. Kerberos? That seems too difficult for most small networks. Don't get me wrong, I don't like LDAP, but there isn't anything better that I'm aware of. LDAP has some support for other applications (for example, we use it for Redmine user accounts), I don't know of anything else besides LDAP that has widespread support. But the initial configuration was a bit of a mess, where I was going back and forth among the official docs, the Ubuntu docs, and other guides. I should write my own guide so that I can add to the confusion.
- jessaustin 10y agoNon-enterprise orgs might just be BYOD plus something vendor-specific like IAM?
- ansible 10y agoMaybe I'm old-fashioned, but I prefer to have a locally-hosted solution.
- jessaustin 10y agoIt's a reasonable preference, but it won't be shared by everyone. Many of us don't even have onsite phone equipment anymore...
- ansible 10y agoYes, I'd get rid of our phone equipment if I could. It has been a hassle. I just wanted to get everyone Skype accounts with dial-in numbers years ago. Well, even if you wanted to cloud-host authentication, what easy solution is there for Linux? Where I can create directories on a local file server and assign groups for restricted access?
- mschuster91 10y agoWell you can host a Docker image of an openldap container, secured by SSL certification (in my experience, Let's Encrypt works for this, just take care to not expose the ldap port, only ldaps) and prevented from unauthorized access by denying anonymous binds. Using service accounts you can then have other cloud services like Atlassian, Slack or Gitlab authenticate against the LDAP server. Ad phone equipment: Asterisk in Docker combined with a VoIP provider (and exposing a SIP server) can work, but I have not tried this in practice. It should support standard Android and iOS SIP clients, but beware that this will drain your battery life due to permanent connections and keepalives - I don't know how easy (and supported) push notifications for calls are. Also, going from the VoIP provider through a questionable (in terms of QoS) Docker hoster to your phone will introduce a measurable latency, and the re-coding that may happen in Asterisk can also negatively affect audio quality.
- dustinkirkland 10y agoAgreed, understood, thanks!
- kwk1 10y agoFreeIPA (https://www.freeipa.org/page/Main_Page https://www.freeipa.org/page/Main_Page) is an LDAP+Kerberos+other stuff implementation which is available in the Ubuntu repositories and is probably a good target for this. If it was easier to set up, I think it would become apparent to more people that it is useful outside the enterprise. For example, if you have a laptop and a desktop, you can set up SSO and an NFS automounted home directory, so you don't need to maintain two (or N) home directories/sets of dotfiles/etc at the same time.
- mschuster91 10y ago> For example, if you have a laptop and a desktop, you can set up SSO and an NFS automounted home directory, so you don't need to maintain two (or N) home directories/sets of dotfiles/etc at the same time. Good luck with unstable network connections. NFS is already enough of a PITA in a fixed office network, much less over e.g. a spotty Wifi. Also you will need a VPN because you don't want to expose raw NFS to the Internet.
- e12e 10y agoI've wondered if maybe zfs send/receive might be press-ganged into working as a substitute for coda/"magically cached nfs"... [ed: In fact I wonder if we (the community) shouldn't be able to bundle up a usable ssh server with less features, protocol 2 only, a great easy-to-use CA, maybe some bonjour/dns srv convention, and some simple db (perhaps ldap is easiest, sigh) and pair that up with ZFS for a minimal, but great, identity-of-user, identity-of-server/daemon cached/networked/encrypted data...]
- kwk1 10y agoYup, all that's true--but just because I mentioned a laptop doesn't mean I'm necessarily talking about an in-network, out-of-network situation.
- mschuster91 10y agoEven in-network can get nasty very soon when you introduce wifi into the mix or have an overloaded switch between the client and the server.