Everywhere I've ever worked the network has been Active Directory (AD). Now AD is fine, it does some things very well.
So a couple years ago at work they brought in MKS Integrity. There was training and the MKS consultant worked in something like "MKS is enterprise, you just log in as yourself using your regular AD credentials". At the time I thought, wow that's cool. It was to me unheard of some app that didn't have it's own separate login module.
Well a couple years have gone by and one of the good innovations in software is that AD integration is now pretty much standard for corporate webapps. It's no longer just a selling point for big iron, enterprise class type software like MKS. I should say I like MKS and I can say it is a solid product line.
At this time AD integration is widely available including in open source systems such as Jenkins. It's to the point where it is now quite noticeable if some app comes along which does not offer AD login out of the box - I'm looking at you Rally! Before it was standard we would just passively accept having separate login to however many corporate apps we used but now it is highly annoying when faced with having to "create an account" and keep track of yet another login and password. It's really inexcusable at this point for any commercial intranet type app to not have AD login out of the box.
In just a couple of years it has become so natural and expected when faced with some new internal web app to of course login as yourself using your network login. What else would you log in as? It's been a good development this standardization around AD integration.
