5 ms·
Uhh what? I'm with you that the days of the "trusted internal network" are coming to an end but you're insane if you think that directories are going away. LDAP
by Spivak 7y ago
Uhh what? I'm with you that the days of the "trusted internal network" are coming to an end but you're insane if you think that directories are going away. LDAP has certainly fallen out of favor but every SaSS user management platform / service is just implementing what are essentially "noLDAP" directories.
What do you think is providing the authentication and user management in those private clouds? OpenLDAP, FreeIPA, ActiveDirectory, Keycloak?
And even when you move everything out of the office to a datacenter you still need all normal IT stuff that you needed in your little office rack just in the datacenter now.
The only part of the "old-guard" IT stack I see disappearing is the office file server.
- whatsmyusername 7y agoIronically the only thing we run locally is file server, and that’s just an AWS storage gateway backed by S3. Its the only reason we still have an ad server.
- EvanAnderson 7y agoManaging groups of Windows client PCs without Active Directory still hasn't reached feature parity w/ Active Directory. I do not welcome going back to the "herding cats" days of "workgroups", personally.
- jedieaston 7y agoAzure AD and Intune is good enough right now if you don’t need local servers for apps, and very cheap (or maybe free) depending on what you buy from Microsoft. It can secure a device, apply ADMX files, install applications, and if you need more complexity then you can run PowerShell scripts. It’s not really user friendly, but AD and GPO never really was either. Did I mention no CALs?
- whatsmyusername 7y agoWe're all Mac. I wouldn't have taken the job otherwise.
- derefr 7y ago> What do you think is providing the authentication and user management in those private clouds? SAML. Yes, the provider's own network probably hosts a directory service as the default SAML backend, but for integrating with enterprise clients who already have their own directories? SAML. Now, rather than making ACL assertions about local users, you have to make ACL assertions about what ACL assertions each foreign directory is allowed to make on behalf of its own "guest" users in your environment.
- gravitas 7y agoSAML is a middle tier between the endpoint (user app) and directory (ADFS, LDAP, etc.) and not a single solution on it's own, it doesn't store data - it provides a means for leveraging that data defined by the schema (e.g. posixAccount and groupMember). It's generally equivalent to pam_sss, nss-pam-ldap and friends at the systems layer of your average Linux. They are complementary, not replacements for each other.
- derefr 7y agoThe difference is that, in practice, if you're "just" a large non-IT enterprise or "just" a cloud provider, then you're not implementing the whole solution any more, only half of it. If you're, say, Box, you're implementing only the endpoint, and mostly don't need your own directory, because all your customers bring their own. If you're, say, IBM, you're implementing only the raw directory, but rely on cloud providers to actually interpret it, rather than hosting any of your own Intranet. And if you're Joe SMB, then you're implicitly using GSuite as your SAML-exposed directory through OpenID Connect, and you don't need an IT department for this at all. (And even if you're an enterprise who also writes your own cloud services, then this is still a change for you, because your endpoints are probably now written "generically" with a SAML interface—treating your own directory as just one among many, talking to it through a public exposure—rather than interfacing directly to it as a privately-configured PAM binding on your servers et al. In other words, now your services [and the departments providing them] are decoupled from your directory, because they both just see each-other through the lens of SAML, and so don't know that your company's employees are any different than a client company's employees.)
- arkanciscan 7y ago"serverless" doesn't mean there isn't a server. Just because I don't need a user/group doesn't mean my cloud won't. Just that I don't need to run one myself. Which is true.
- stcredzero 7y agoevery SaSS user management platform / service is just implementing what are essentially "noLDAP" directories We need a buzzword for these. "lolDAP?" https://xkcd.com/927/ https://xkcd.com/927/
- AnIdiotOnTheNet 7y agoOffice file server isn't going anywhere as long as there are places where internet isn't at least dozens of Mb/s in each direction, and I assure you there are still many, many such places.
- jiggawatts 7y agoTo add to this: it will be forever impossible to provide low latency to all sites of any large, distributed organisation. For some categories of applications, it'll always be much more performant to have local servers, even if the network is 100Gbps symmetric fibre.
- closeparen 7y agoTrue, but you can also spin up replicas in your cloud providers' nearest regions. Everybody talks about capacity elasticity, but easy geographical distribution is the much cooler property of public clouds IMO. I could drive to a local colocation site and maintain my own boxes if it came to that, but having dozens of datacenters around the world would be physically impossible for me otherwise. Of course your applications have to support that, but if they can be distributed across in-office servers then they already do.