These slippery people.
For me, it’s all about identity and access management these days.
How to disambiguate users without relying too heavily on the classic “identity theft” data.
How to handle ad hoc registration and secure communication with hundreds of thousands of transient users.
How to make sense of business rules to build them into approval chains in user provisioning. (This is the sticky part. There are always unwritten rules that bubble to the surface. “All users have to be approved for access to that data, so that data owner needs to sign off on it.“ “What about the developer writing the application? Does he have to get approval too?“ “Oh no, he can create as many test accounts as he wants.“)
How to consolidate management of access to ALL the platforms, and no, I don’t just mean single sign-on through Citrix. Is a system administrator going to go through Citrix to log in to the console of a misbehaving Linux box? I don’t think so. Are you going to get your third-party financial application to log in to a local system account through Citrix? Nuh-uh. Please don’t tell me there’s a silver-bullet single-signon solution out there that handles ALL access control, because it’s still only modeled on the Windows-using non-IT employee.
I’m probably going to be spending the next two years solving this problem, and some of my choices are going to be made for me midstream, because I’m dealing with an imminent outsourcing as well.
All in all, I think I’d rather be doing my taxes.


Single sign-on is one of those things I hear about a lot, but I have yet to see how it works in reality other than feel-good case studies or just piggy-backing on AD/LDAP. There’s always something that is a one-off or two-off such as an internal web app to track employee learning that requires its own login, or non-Windows boxes that should rather be managed out of band via SSH. Heck, one of my coworkers (a network analyst) just last week complained that it takes too much of his time to log into our ticketing system every morning because it is not tied into AD. I sat there kinda wondering why sysadmin types would ever complain about that; I always expect non-technical people to have the least tolerance to more accounts and logins…
I dunno. I like the feel-good qualities of single sign-on, but I don’t get how they will be effectively realized in anything but a small company. This may just be my ignorance showing through, however, and it might be easier than I am aware.